in reply to Re: Persistant Perl arguments ( pperl )
in thread Persistant Perl arguments ( pperl )

Thanks for the reply mischief, however your example uses "/usr/bin/perl" not "/usr/bin/pperl". Maybe I don't understand, but heres the scenario. This script will be called as a cgi file, so I can not run via the command line, but I still need to get that --prefork=25 option whenever apache hits the file. Your example uses /usr/bin/perl and just ignores the option. If I use your method with /usr/bin/pperl I get the following.
#!/usr/bin/pperl -- --prefork=25 print "\n\nHELLO\n";
Output:
Can't open perl script "--prefork=25": No such file or directory pperl: perl script failed to start: No such file or directory
Let me know if I'm not making any sense!

Replies are listed 'Best First'.
Re^3: Persistant Perl arguments ( pperl )
by mr_mischief (Monsignor) on Apr 28, 2008 at 19:03 UTC
    On further examination, it looks like you can't use pperl properly from the shebang line. It appears to be intended to launch a separate program to be named on the command line only. See my update at Re: Persistant Perl arguments ( pperl ) for more info.