The mailing list for listmasters using Sympa

["Eric Sandquist" <address@concealed>]

Thanks for the patch...  I am trying it now...

I did try changing 'log_socket_type' in sympa.conf to 'inet', but then there
was no logging at all for sympa..  Although, the processes did continue to
run an did not die ;)

I have now set the 'log_socket_type' in sympa.conf to 'unix' and attempted
to apply the patch... Patch appears to be for a different version.. I am
running 3.4.2..



Eric
-----Original Message-----
From: Olivier Salaun - CRU [mailto:address@concealed]
Sent: Tuesday, February 11, 2003 7:59 AM
To: Eric Sandquist
Cc: address@concealed
Subject: Re: [sympa-users]processes dieing for unknown reason...


You might fix your problem with :
        * either change 'log_socket_type' sympa.conf parameter
        * or apply attached patch against Log.pm. It will prevent Sympa from 
trying
to
          reconnect to syslogd if connection was lost.

Please keep us informed which solution worked for you...

Eric Sandquist wrote:
> Well... Syslogd has been running the whole time.. All other loggins seems
to
> be working just fine...  Last weeks re-attempt at this yielded this error:
>
> connect: No such file or directory (SOCK_DGRAM after trying SOCK_STREEM)
at
> /www/sympa/bin/Log.pm line 96
>
> Is it possible, then, that syslogd is unavailable due to another process
> writing to it?  If so, is there another way for me to redirect of handle
the
> logging?
>
> Sever load has been very low over all - .86-1.40...  So this does not seem
> to make sense...

--
Olivier Salaun
Comite Reseau des Universites