David,
> >I've obviously gone mental this week. ;-) I looked at the
> >ownership/permissions on /var/log/httpd but for some reason didn't look at
> >the parent directories. The problem was incorrect permissions on the log
> >directory.
>I considered and discarded that thought, because the bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Sisler wrote:
>I've obviously gone mental this week. ;-) I looked at the
>ownership/permissions on /var/log/httpd but for some reason didn't look at
>the parent directories. The problem was incorrect permissions on the log
>directory.
I c
I've obviously gone mental this week. ;-) I looked at the
ownership/permissions on /var/log/httpd but for some reason didn't look at
the parent directories. The problem was incorrect permissions on the log
directory.
My thanks to those who offered advise.
-Eric
Eric Sisler
Applications S
David Talkington <[EMAIL PROTECTED]> wrote:
> >It appears as though apache's child process isn't able to open or create a
> >lockfile, but I'm not sure what to do about it. Ownership/permissions on
> >/var/log/httpd are root:apache and 775.
>... But that's not the directory that it's whining ab
Michael Sorrentino <[EMAIL PROTECTED]> wrote:
>I had a similiar problem with apache when upgrading to the latest kernel
>however I don't recall exactly what the error was. Anywhoo, the problem
>turned out to be I somehow missed the mod_perl update. Make sure you've
>installed that RPM.
I wish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Sisler wrote:
>
>It appears as though apache's child process isn't able to open or create a
>lockfile, but I'm not sure what to do about it. Ownership/permissions on
>/var/log/httpd are root:apache and 775.
... But that's not the directory th
I had a similiar problem with apache when upgrading to the latest kernel
however I don't recall exactly what the error was. Anywhoo, the problem
turned out to be I somehow missed the mod_perl update. Make sure you've
installed that RPM.
On Thursday 04 April 2002 10:27 am, you wrote:
> Greeting
