It seems that there are two issues here, one for gutsy and one for dapper. The issue that was reported is for gutsy and shouldn't apply for dapper.
In dapper, the reload action in the init script stops then starts the syslog daemon. In gutsy, the reload action in the init script sends a HUP signal, which is the reason why it has problem reopening files when run under the syslog user. For dapper users, did you change the cron script or the init script ? -- Various problems running syslogd with "-u syslog" option https://bugs.launchpad.net/bugs/120085 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
