On Thu, Sep 06, 2007 at 09:32:48PM -0000, Mathias Gug wrote: > I've attached a debdiff that should fix the issue in gutsy. > > I've looked into the suggestion of dropping the root privilege before > init. However it won't work as init parses the configuration file to > open the log files. If network logging is required (which is only known > after the configuration file is parsed), syslogd needs to bind to a > system port, which can only be done as root. > > Instead, I've patched the init script to start syslogd with the -u > option. Before starting syslogd, all the log files that syslogd will > open have their ownership fixed. That should fix the issue, as long as > the init script is used to start/stop/reload syslogd. > > ** Attachment added: "sysklogd_1.4.1-21ubuntu3.debdiff" > http://launchpadlibrarian.net/9156609/sysklogd_1.4.1-21ubuntu3.debdiff
Shouldn't the cron script be fixed to set correct ownership as well? -- - mdz -- 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
