Thanks Jeff and Doug! Both of your were right after all. The culprit was
indeed, /dev/null. I'm not a unix guy, so it took me a while to track this
problem down. It turned out that for some reason, the system didn't see
/dev/null as a character device, plus the permissions were screwed up. I
don't know what had caused this and I don't know why mod_perl was the only
piece of software that had problems with it, but at least it's fixed now.
Thanks again
Dmitry
At 01:01 PM 10/4/99 , Jeff Beard wrote:
>At the risk of irritating you by pressing the issue, I have to agree with
>Doug, and I've had the same problem with the exact same errors.
>
>My null device worked fine for me but the permissions were changed on it so
>that certain other processes couldn't use it (i.e. apache).
>
>Until I cornered the process that was changing the perms on it, I had to
>remove it and mknod it again.
>
>:
>:
>: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.
