Comment 13 for bug 120085

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.