Date: Sat, 11 Jul 1998 14:41:59 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: dg@root.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... Message-ID: <199807111841.OAA27314@khavrinen.lcs.mit.edu> In-Reply-To: <19980711000956.A21101@klemm.gtn.com> References: <199807101111.NAA00658@magnet.geophysik.tu-freiberg.de> <19980711000956.A21101@klemm.gtn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Sat, 11 Jul 1998 00:09:56 +0200, Andreas Klemm <andreas@klemm.gtn.com> said: > No daemons dying here. Which version (date) of -current do > you use ? Might that be a hardware related thing ? An interesting note I might make: When I was running diablo, I would see `daemons dying' quite regularly. Right now, I'm running a beta of Cyclone, which has a serious memory leak. It eats up all available memory within two hours. I don't see `daemons dying' fairly often. My suspicion is that the problem in question is specific to the situation where the program requesting the memory is NOT the one which gets killed. When I'm running cyclone, it is by far the biggest hog, and it's a single process; the system kills it off, and the next top-hour a cron job runs which restarts it without incident. When I ran diablo, however, I don't recall anything ever getting explicitly killed by the system. Diablo consists of about 100 separate, small processes all running simultaneously, half of which are driven by a cron job. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807111841.OAA27314>