I have reported this to linux-kernel and since apache initially opens access logs as root and then fails to write to them, people on linux-kernel believe it is an apache problem.
I have no idea either way. I'm just reporting it to both sides for a developer to figure out. I understand that it may be a bad idea to do logs over nfs, but regardless of what is a smart thing to do, it should still work. -jeremy > Synopsis: writing access logs over nfs > > State-Changed-From-To: open-closed > State-Changed-By: marc > State-Changed-When: Sat Aug 1 13:48:39 PDT 1998 > State-Changed-Why: > No, it is not an Apache problem. As I have already told > you, this is an issue with your OS. Two possible problems > are that root is remapped remotely (you say you disabled > that but that doesn't necessarily mean it did what you > want...) or Linux's NFS does not follow Unix fs semantics with regards to > access > permissions after a setuid(). > > Not only that, but NFS just isn't reliable for logging and > is a very poor idea. > > See also PR 452. > > http://www.xxedgexx.com | [EMAIL PROTECTED] | pgp available from: | http://www.xxedgexx.com/pgp.html
