Why mark it as invalid? The current settings simply make nginx unable to write logs. I can confirm that the master runs as root and manage logs, since changing logrotate settings to root root make it work as expected.
On Sat, Mar 13, 2010 at 1:06 PM, Dulmandakh Sukhbaatar <dulmand...@gmail.com > wrote: > on Lucid log files owned by root and groups is also root, but can write > logs to it. from 'ps aux | grep nginx' I can see that there are 2 nginx > processes on is master and another is worker. worker process is serving > pages and running as a www-data user. but master process is managing > workers and logs I think, and running as a root user. without root it > cannot bind to port lower 1024. > > I think that this bug is not valid. how about marking it as INVALID? > > -- > nginx logrotate conf file sets wrong owner for the log > https://bugs.launchpad.net/bugs/499494 > You received this bug notification because you are a direct subscriber > of the bug. > -- nginx logrotate conf file sets wrong owner for the log https://bugs.launchpad.net/bugs/499494 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
