general/4006: JServ cannot write to jserv.log unless this file is manualy chmod to 0x666

[Masoud Loghmani <ma...@earthlink.net>]

>Number:         4006
>Category:       general
>Synopsis:       JServ cannot write to jserv.log unless this file is manualy chmod to 0x666
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Mar  5 10:10:01 PST 1999
>Last-Modified:
>Originator:     masoudl@earthlink.net
>Organization:
apache
>Release:        Latest
>Environment:
SunOS 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-2
>Description:
JServ needs to have write access to $HTTPD/var/apache/log/jserv.log
because when the file is created initialy, Apache is running as
root, but then it changes to "nobody", and as such it does
not have permission to writ to jserv.log. 
The solution is to manually chmod 0666 jserv.log after it is
created, and then restart apache. 
It would be much better for apache to chmod this automatically,
or to chown the file after it is created to nobody.
>How-To-Repeat:

>Fix:
Yes, look at the bug info.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]