On 30/11/10 11:38, Michael Biebl wrote: > On 01.10.2009 08:31, Christoph Martin wrote: > >> I use the syslog-tls feature to send syslog messages from a bunch of host >> to a centralized rsyslog server. On initial startup of rsyslog on >> the syslog server it consumes allready about 170M. If I only have one >> client which sends syslog messages it stays like this. But when I >> start the syslogs senders on one to three other host, the memory >> quickly (in minutes) goes up to 2G. The machine then goes in to >> swapping and is mostly unusable. >> > Hi everyone, > > I cherry-picked the fix from upstream Git and uploaded it as 4.6.4-2. > > Please test this version and let me know if that fixes your problem. > > I'll then ask for a freeze-exception, so this fix get's into squeeze. > > Thanks, > Michael > Thanks Michael!
It appears so far to be working fine. It's around 4 hours now and I've not seen any behaviour the older version uses to do in just 20 minutes. Thanks! :-) Cheers, Dererk -- BOFH excuse #306: CPU-angle has to be adjusted because of vibrations coming from the nearby road
signature.asc
Description: OpenPGP digital signature
