On Tue, 2005-05-03 at 21:40 -0700, Daniel Kegel wrote: > I'm running distccd-2.16 in daemon mode on some old 2.2 kernel boxes. > After 120 days of uptime, the daemons became unresponsive. > First it affected one machine, then another, and finally all of them. > Restarting the daemon fixed the problem. > Anyone seen anything like that before?
I have not. I can believe that perhaps its preforking model rolls over some kind of counter in 2.2 after that much time. Wasn't there a 2.2 or 2.0 release that needed to reboot after 1<<32 ms? I can't think of anything specific that would cause it but I'd suspect a 2.2 networking bug. -- Martin ps: congratulations :-)
signature.asc
Description: This is a digitally signed message part
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc
