Syslogging broken - culprit found

[Julian Field]

On 27/3/09 09:44, Tom Weber wrote:
> Am Freitag, den 27.03.2009, 01:11 +0000 schrieb Julian Field:
>
>    
>>> Without looking at the code, since my eyes are about to finally freak
>>> out now, i guess you integrate the razor perl modules directly in
>>> MailScanner which then initialize/openlog the Syslog again and mess it
>>> up.
>>>
>>>        
>> I don't call Razor at all, I leave SpamAssassin to do that. I suspect
>>      
> Yeah, of course. I put this wrong. The result is the same though (MS
> importing SA importing razor).
>
>    
>> that it's just the SA initialisation call that is screwing with it. I
>> could always just call the Log::initialise function again after
>> initialising SpamAssassin, that *shouldn't* have any major consequences.
>>      
> I personally don't care that much about razor logging to syslog. But
> these Side-effects should be eliminated.
>    
Absolutely agreed. I have added some code which will work around this 
problem, which will be in the next release.
>    
>>> Maybe someone else wants to verify this on a non debian system too, but
>>> i'm quite confident that this is the cause for the behaviour.
>>>
>>>        
>> Please can someone do this for me?
>>      
> May I add that this is not how debian ships. The debian default for
> razor is to log into a file not using syslog at all.
>
> All my MailScanner installations are linux-vservers which I usually
> derive from a tared up template. For some reason I had changed this
> setting somewhere in the past and it made it into my template resulting
> in a couple of MailScanner Installations with this behaviour.
>
>    Tom
>
>    

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.