FS#5173 - Lighttpd: doesn't honor server.username and server.groupname for log dir.

Attached to Project: Arch Linux
Opened by Martin Skytte (marteus) - Sunday, 06 August 2006, 12:14 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 22 November 2006, 20:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When lighttpd archives it's logs and creates a new one the new one is owned by nobody:nobody (the initial owner/group) and not by the ones set in server.username and server.groupname in /etc/lighttpd/lighttpd.conf.

This makes lighttpd fail to run (though the daemon says otherwise) and leads to severe php-cgi memory leaks.
This task depends upon

Closed by  Tobias Kieslich (tobias)
Sunday, 17 December 2006, 19:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  added a comment into lighttpd.conf right above the username and group settings
Comment by Tobias Kieslich (tobias) - Saturday, 26 August 2006, 22:25 GMT
this happens due to the fact that the logrotation happens independently from the lighttpds dominion. It's written in the logrotate.d files. The default is set to the same default as in the lighttpd.conf. There is no way making logrotate honouring settings in lighttpd.conf. This task is up to the admin that changes the values in lighttpd.conf. So you wanna change the corresponding line in /etc/logrotate.d/lighttpd. Make sense?
Comment by Martin Skytte (marteus) - Saturday, 26 August 2006, 22:31 GMT
Kinda, but I would have liked that info commented in /etc/lighttpd/lighttpd.conf though - as it is not quite obvious (to me).
Comment by nackd (Prieto) - Tuesday, 07 November 2006, 21:17 GMT
I agree a comment in lighttpd.conf would be helpful.

Loading...