Re: problem with error_log_spread.pl

You might try upping the listen() backlog queue in the spread sources as 
Yair alluded to....


Jay West wrote:

>Theo wrote...
>
>>Add after:
>>
>>   print STDERR "Failed multicast $_ to $group: $sperrno\n" if $debug;
>>+ Spread::disconnect($mbox);
>>+ ($mbox, $privategroup) = Spread::connect(\%args);
>>
>>That will attempt a reconnect after every failed multicast attempt
>>
>ensuring
>
>>that as soon as Spread is available, it will log.
>>
>
>Ok, I will try that. But that won't get rid of the "Could not connect"
>messages would it? What I think will happen is spread will still
>sporadically fail to connect, but when it tries to send a message it should
>try to reconnect. That should work, but the programmers will see all the
>"could not connect" messages and call me at midnight *GRIN*. I think I will
>make the above suggested patch, it's a good idea to have it do that. But
>I'll also dig into the O'reilly perl book and see about having it try
>multiple times for the initial connect before giving up.
>
>Thanks!
>
>Jay West
>
>---
>[This E-mail scanned for viruses by Declude Virus]
>
>
>_______________________________________________
>mls-users mailing list
>[email protected]
>http://lists.backhand.org/mailman/listinfo/mls-users
>