Thanks for upping the priority ... I just tried it, and this also happens if lighty is not automatically started in a runlevel. It just starts (or at least tries to start) at 22 minutes after the full hour (logrotate) - this may even be an upstream bug, i guess it's the same in debian (don't have any debian installed right now to test)
-- lighttpd reload executes restart (bad on logrotate!) https://bugs.launchpad.net/bugs/393792 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
