> >From the mod_perl guide:
>
> syntax error at /dev/null line 1, near "line arguments:"
> Execution of /dev/null aborted due to compilation errors.
> parse: Undefined error: 0
> There is a chance that your /dev/null device is broken. Try:
> % sudo echo > /dev/null
>
> This is exactly the problem I have been getting when starting Apache
> mod_perl, however the suggested fix does not work for me. We're on a
> HPUX 11 machine. Is there another way to solve this problem? As I
> understand it, if /dev/null is being used as the $0 argument to the
> handler, perhaps I could somehow explicitly set it to another (empty)
> file? How would I go about that?
I've never seen this to be an actual /dev/null problem. I've seen this in
HTML::EmbPerl and Apache::Registry, where the "/dev/null" is what gets put
in $0 when mod_perl has lost track of the original filename (and line 1
because it forget WHERE it was, too :-).
According to the sample:
> syntax error at /dev/null line 1, near "line arguments:"
> Execution of /dev/null aborted due to compilation errors.
> parse: Undefined error: 0
Which says to me that one of your (scripts/server-parsed pages/modules) has
the string "line arguments:" in it, and there is a syntax error near there.
So (for example, on my Linux system):
find /home/httpd /etc/httpd/lib/perl -type f -exec grep -l 'line arguments:'
{} \;
the result should show you which file to fix.
HTH!
L8r,
Rob
