I guess that the files are pre-created with the wrong user permissions (who is the owner)? Usually, this happens if some external script creates them.
Rainer > -----Original Message----- > From: Petri Lehtinen [mailto:[email protected]] > Sent: Friday, April 08, 2011 8:25 AM > To: [email protected] > Cc: Rainer Gerhards > Subject: Re: rsyslog, fifos and SIGHUP > > Rainer Gerhards wrote: > > > -----Original Message----- > > > From: Petri Lehtinen [mailto:[email protected]] > > > > > > I'm using rsyslog 4.2.0 on Ubuntu Lucid and I'm having problems with > > > a fifo. It seems that rsyslog stops writing to the fifo when it > > > receives the SIGHUP signal. This is problematic, as, in Ubuntu's > > > default configuration, logrotate HUPs rsyslog every day. > > > > > > Is this a known issue, has it been fixed in later versions? Can I do > > > anything to help fix this issue? > > > > Two things: a) the version is pretty old, b) Ubuntu drops privileges, > > but their config is often not really up to that. Keep running as root > > for a test and check if the problem re-occurs. I guess not. > > I commented out the "$PrivDropToUser syslog" and "$PrivDropToGroup > syslog" lines from /etc/rsyslog.conf, and it started working. > > Any ideas on how to make the config "up to" running as non-root, so that the > HUP+fifo combination works? My configuration (the Ubuntu > default) is available at: > > https://gist.github.com/909386 _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
