Comment 74 for bug 407862

Nikolaus, can you provide exact steps to reproduce the problem for you?

I have a fully up-to-date 10.04.3 LTS. /var/log/syslog is owned by syslog:adm. Note that if your file does *not* have these ownerships, you should `sudo chown syslog:adm /var/log/syslog` before you begin.

$ tail -f /var/log/syslog
# In another shell
$ logger testing
# testing shows up in syslog
# In another shell
$ pkill -HUP rsyslogd
# In the tail, I see the 'HUPed... lightweight' message
$ logger testing
# The message shows up in the tail

So that all looks to work perfectly. /var/log/syslog is still owned by syslog:adm. Now I do

$ logrotate --force --verbose /etc/logrotate.conf

All the logs get rotated, and /var/log/syslog is still owned by syslog:adm, and it contains the 'HUPed...lightweight' message. Writing a log message to it continues to work fine.