From owner-freebsd-current Wed Nov 18 18:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25811 for freebsd-current-outgoing; Wed, 18 Nov 1998 18:47:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-10.dialip.mich.net [192.195.231.212]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA25805 for ; Wed, 18 Nov 1998 18:47:50 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811190247.SAA25805@hub.freebsd.org> Received: (qmail 92221 invoked from smtpd); 19 Nov 1998 02:47:17 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 19 Nov 1998 02:47:17 -0000 Date: Wed, 18 Nov 1998 21:47:16 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: more dying daemons To: current@FreeBSD.ORG In-Reply-To: <199811190040.QAA12276@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Nov, I wrote: > > I'm still having the problems I described earlier. > inetd, samba, and ssh exhibit symptoms where they wither away and die > after a certain amount of time, and this is easily and rapidly > reproducible (in the space of only an hour my freshly-started inetd will > begin to die each time it forks...) > while sitting here trying to find a common thread through all this mess... it appears to happen only with servers that fork() copies of themselves on incoming requests. inetd does this, samba does this, and sshd does this. consequently, inetd dies, samba dies, and sshd dies :) however, servers that *don't* fork off a new connection on incoming requests don't die. a good example is mysql. i've never had a problem with it dying, even though it gets swapped out much more often than the other servers (it is rarely used)... another example is httpd which only has problems when its heavily used (i'm guessing that it has run out of pre-forked copies and has to fork off new children) so, it looks like a problem where parts of a daemon are swapped out and then when the daemon forks, some of the pages are never paged back in? i dunno, a guess at least :) that should help narrow down the source of the problem dramatically. when i get a free moment i'll try going through the commits on various parts of the vm subsystem and see what i can dig up... enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message