Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#11080 - lighttpd cannot open error log by default
Attached to Project:
Arch Linux
Opened by Aaron Griffin (phrakture) - Thursday, 31 July 2008, 18:48 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 31 July 2008, 22:27 GMT
Opened by Aaron Griffin (phrakture) - Thursday, 31 July 2008, 18:48 GMT
Last edited by Pierre Schmitz (Pierre) - Thursday, 31 July 2008, 22:27 GMT
|
DetailsDue to the redirect in the rc.d script, the default lighttpd install cannot open /var/log/lighttpd/error.log
This is due to the fact that the >> and errorlog setting point to the same file, and both cannot open it for writing. Changing one of these to a different file makes it functional. |
This task depends upon
Closed by Pierre Schmitz (Pierre)
Thursday, 31 July 2008, 22:27 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in [testing]
Thursday, 31 July 2008, 22:27 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in [testing]
Comment by Pierre Schmitz (Pierre) -
Thursday, 31 July 2008, 22:26 GMT
I just copied the rc-script from the old package. I remove that redirect now. Normaly lighttpd should log errors in its log without this. If this also fails one still cann run it directly; which is the same behaviour like apache.