Comment 80 for bug 407862

Revision history for this message
surfingalien (inairtas) wrote :

i'm making this discussion come up as i have the same problem as described on 3 diferent machine all running ubuntu 10.04 (2 laptops and 1 server). if this is not so important for the laptop, it counts for my server as i usually read the syslog to see if evrything works fine... without a log file, i'm coming blind...

I didn't change any permisions on any file on these machine. for example I had this bug on my server last week, and reinstalled it 7 days ago. reading the syslog a couple of days after it shows:

jean-louis@x-wing:~$ tail -100 /var/log/syslog
Jan 21 06:40:30 x-wing rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="2173" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'.
Jan 21 07:17:01 x-wing CRON[3990]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 21 08:17:01 x-wing CRON[4003]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 21 09:17:01 x-wing CRON[4017]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

when googling: rsyslogd was HUPed, type 'lightweight' there are thousands of links coming up, then this is not an isolated problem.

what should be done to solve this issue ?

i am available for any information, and can even provide an access to a machine if i can help solving.