Date: Mon, 10 Aug 1998 09:11:24 +0300 (EEST) From: Alexander Litvin <archer@lucky.net> To: current@FreeBSD.ORG Subject: Re: Reminder : can't fork Message-ID: <199808100611.JAA07064@grape.carrier.kiev.ua> In-Reply-To: <199808092253.PAA07594@rah.star-gate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199808092253.PAA07594@rah.star-gate.com> you wrote:
AH> Well okay, lets see if others report the same problem.
Hmm, description of the problem was quite short, so I didn't understand
whether that was notorious "daemons dying". If it is, who said it is
gone?
And it seemed to me, that agreement was achieved on that it cannot
be explained just by memory overcommit. I don't mind if the system
kill my processes when out of swap, but why should all forked sendmails
get SIGSEGV 8 hours after the "out of swap" condition was gone?
It is easy to reproduce. What looks strange to me is the
following.
I wrote a "dummy" daemon -- just simple prog which daemonised
and then periodically forked to do some dummy work. I tought
it whould be easier to debug the problem with simple prog.
I have not been able to make it fail. Though sendmail and
cron still die. What is different between them and my daemon?
AH> I will play with my system tonite when I get home from work.
AH> Cheers,
AH> Amancio
---
Unix is the worst operating system; except for all others.
-- Berry Kercheval
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?199808100611.JAA07064>