[syslog-ng]PTR lookups; leak/crash fixes

[Scott McDermott]

Scott McDermott on Thu  5/10 15:59 -0400:
> > > I bet it starts eating your CPU and RAM until your computer
> > > explodes ;)
> > > 
> > > But we'll see over the next few days...also it HUPs each night
> > > when the rotation occurs, so perhaps that does a lot of freeing
> > > and we'll get some stable behavior.
> > 
> > [...] I haven't actually had any trouble with syslog-ng on Linux
> > since around 1.4.5 or so...  Anyhoo, YMMV I suppose. 
> 
> [...] Try accepting from other machines via TCP, that seems to invoke
> the strange behavior better.  I'm also using chain_hostnames which
> might have something to do with it...more string ops.  Here's my ng
> process:
> 
> USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
> root     18717 27.4  4.3  6268 5572 ?        R    Oct04 642:10 syslog-ng
> 
> on 333Mhz PII.  The VM use seems steady though...we'll see tomorrow.

No such luck.

USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root     18717 33.8  6.4  8976 8280 ?        R    Oct04 1169:12 syslog-ng

Just keeps going up and up, with both CPU and RAM.