(RADIATOR) Memory Leak problem

[Olivier Macchioni]

PREVOSTO, Laurent wrote:

>>We fixed it by removing the <SYSLOG> clause :
>>
>>#<Log SYSLOG>
>>#        Trace           4
>>#        LogSock         udp
>>#        LogHost         172.16.4.241
>>#        Facility        local0
>>#       MaxMessageLength 1000
>>#</Log>
>>
>>We have numerous other servers running the same version of 
>>RADIATOR, none of them shows the same behaviour.
>>
>>Olivier
>>
>>    
>>
>
>I've upgraded Syslog.pm to the last version since the one provided with the perl package is pretty old.
>We'll see if things get better this way.
>By the way, did you try upgrading to 3.15 ? Did it solve the problem ?
>Commenting out <Syslog> is a solution but i can't afford it : we do need logs for troubleshooting...
>
>Regards,
>
>Laurent
>

No, we didn't test any other option - Syslog is not really needed there, 
so we're just relying on the regular logfiles.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.