Not answering your mod_perl question here, but I believe this
suggestion in the guide isn't useful advice in any event --
this isn't 'echo'ing to /dev/null as su (root); rather it's 'echo'ing
a line as su, and you (normal user) are redirecting that output to
/dev/null.
I.e., the grouping of that command is like so (yeah, I know, this is
in no way intended to be real shell syntax, just to show the
semantics...):
(sudo echo) > /dev/null
rather than:
sudo (echo >/dev/null)
Not sure what is trying to be accomplished by either of these, but in
the interests of clarity in the guide, I think this ought to be either
corrected or removed entirely. I'll volunteer to make the changes, if
someone can clarify exactly what the intended result is.
Stas? What do you say? Am I missing something here?
<Steve Reppucci>
On 28 Mar 2001, Matthew Kennedy wrote:
> Hello,
>
> >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?
>
> Does anyone have any suggestions?
>
> Thanks,
>
> Matt
>
--
=-=-=-=-=-=-=-=-=-=- My God! What have I done? -=-=-=-=-=-=-=-=-=-=
Steve Reppucci [EMAIL PROTECTED] |
Logical Choice Software http://logsoft.com/ |
