Hi Roboticus, unfortunately, the perl installation is on a common automounted partition, that is shared across all platforms. We run almost entirely on servers, and don't have individual machines. Also, if I have a script that has
#!/common/bin/perl
and this resolves to:
/common/bin/perl -> <perlpath>/bin/perl
so that the common executable path is a link to the wrapper, you still have the same problem: i.e. the unix kernel can't exec the file
<perlpath>/bin/perl, because it's not binary, and doesn't return the "magic number". So, the perl script just gets parsed by
/bin/csh, which croaks...
I'm really thinking there is no good solution to getting <perlpath>/bin/perl to trick the kernel into thinking that it's a real binary shell interpreter...
