Yes, I have been trying to track it down. I have had several reports
of this, but have been unable to reproduce it myself. If someone
comes up with a way to reliably reproduce this problem, please let
me know. I've been writing a series of tests to try to reproduce it.
Driving the load up, multiple simultaneous connections, many connections
exiting at the same time, etc. None of my tests have been able to
cause this problem yet.
Rob
On Fri, Aug 03, 2001 at 11:24:16AM -0400, Trond Eivind Glomsrød wrote:
> "Eric Wood" <[EMAIL PROTECTED]> writes:
>
> > Every other day I have to restart xinetd:
> >
> > /var/log/messages show: Aug 3 08:16:29 seawolf xinetd[5539]: execv(
> > (null) ) failed: Bad address (errno = 14)
> >
> > Bug reported as: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=48367
>
> It's not easily reproducible.
>
> It doesn't happen under heavy load testing. However, there are
> separate reports and it has been found internally as well by people
> using it - but no way to properly reproduce it.
>
> Changing options, or just removing the patch for fixing file logging,
> doesn't seem help.
>
> --
> Trond Eivind Glomsrød
> Red Hat, Inc.
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
