> 2013/2/19 Rainer Gerhards <[email protected]> > > > On Tue, 2013-02-19 at 11:50 +0100, Xavier Fustero wrote: > > > Hi, > > > > > > is there a final solution for this problem? > > > > > simple answer: not yet. Ping me early march, except.. > > > > > Even commenting the PrivDrop lines doesn't work for me. "service > > > rsyslog start" keeps in foreground for a while and finally dies > > > (using -n in /etc/init/rsyslog.conf). It behaves like is described in this > thread. > > > Creating two pids and writing the forked one under /var/run/rsyslog.pid. > > > > > if someone can canfirm this, which would boost the priority (I have > > two conferences in front of me and am hyper-busy right now...). > > > > I don't remember any issues without PrivDrop. Although I'm also super-busy > now, but I'd gladly help with testing on Ubuntu and CentOS in early March.
This patch: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=0114b531b38b16db98b04b680017d6c758987fd9 (for v7-stable) should also fix the hang. I'd appreciate if you could give it a try and report back. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
