Nay, my null device works just fine, but I still keep occasionally getting
these errors for most of mod_perl config directives. One additional piece
of information: it seems that every time this problem shows up, I can get
rid of it simply by rerunning apache's autoconf.
I can't see any physical connection between the two, but then again, I
don't know much about autoconf. I would appreciate if anyone could point
out what the connection is.
Regards
Dmitry
At 11:55 AM 9/21/99 , Doug MacEachern wrote:
>no, but I've seen it before, your /dev/null device is broken.
>try:
>
>% sudo echo > /dev/null
>
>On Wed, 15 Sep 1999, Dmitry Beransky wrote:
>
> > Hi,
> >
> > My apache/mod_perl combo had been running just fine until yesterday when
> > all of a sudden (I can't recall making any changes to the setup) all
> > configuration lines containing commands Perl*Handler and PerlModule
> started
> > giving me the following error message:
> >
> > root# apachectl configtest
> > syntax error at /dev/null line 1, near "line arguments:"
> > Execution of /dev/null aborted due to compilation errors.
> > parse: Undefined error: 0
> >
> > Any ideas what might have caused this?
