Philip, I wil try to set up this as well. In the mean time, could you tell me if it happens with the plain 5.3.6 or with the newer git tree (with the patch). Without the patch, I can already see why it can happen, with it, I do not yet have a clear understanding of the issue.
Thanks, Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Philip M. Gollucci > Sent: Sunday, January 17, 2010 12:56 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 5.3.6 (v5-beta) released > > On 1/17/2010 6:51 AM, Michael Biebl wrote: > > As an additonal hint: If I start xconsole (a process reading from > > /dev/xconsole) before I start rsyslogd, then the crash does not > occur. > Possibly related, on FreeBSD in a jail if rsyslog ever tries to write > to > /dev/console, it loops in a extremely tightly loop consuming 100% of > the > core its on. [see -dn output, possibly with ktrace/kdump] > > Eventually it will consume all the memory on the box and it will go > boom. > > > -- > ----------------------------------------------------------------------- > - > 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C > Philip M. Gollucci ([email protected]) c: 703.336.9354 > VP Apache Infrastructure; Member, Apache Software Foundation > Committer, FreeBSD Foundation > Sr. System Admin, Ridecharge Inc. > Consultant, P6M7G8 Inc. > > Work like you don't need the money, > love like you'll never get hurt, > and dance like nobody's watching. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
