From owner-freebsd-questions@FreeBSD.ORG  Fri Dec  6 15:11:35 2013
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F0F66442
 for <freebsd-questions@freebsd.org>; Fri,  6 Dec 2013 15:11:35 +0000 (UTC)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C1CE5159C
 for <freebsd-questions@freebsd.org>; Fri,  6 Dec 2013 15:11:35 +0000 (UTC)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AEA7A20EE5
 for <freebsd-questions@freebsd.org>; Fri,  6 Dec 2013 10:11:30 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute5.internal (MEProxy); Fri, 06 Dec 2013 10:11:30 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=ohayU0SiOIdBDfn84kYjSJ9GCPY=; b=sA/
 nZFuT9WugjC4Olp5ZE4lCpXj+FObsnmq30rAMpB4pK6DwaW3v+gnpnbr1uHBW0aH
 l+PKp2gt+ktvQdgrAYOgUiE5aR3oXmZBa6XXRrhEEwsWzzBUfTd+DkuZ80Xvkb5Y
 drJLkdJ9XgyLsCoebMeEx9smEWI6B0DPOnJhq+4k=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 5A72A107ABC; Fri,  6 Dec 2013 10:11:30 -0500 (EST)
Message-Id: <1386342690.25172.56361253.28A1E4DA@webmail.messagingengine.com>
X-Sasl-Enc: TlGbcynLDDnF6oRiqYIQ4Y6MeVdGArqrMp4vEbC35mp1 1386342690
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-c99dcdd8
In-Reply-To: <1386092314.98211.YahooMailNeo@web161904.mail.bf1.yahoo.com>
References: <1386092314.98211.YahooMailNeo@web161904.mail.bf1.yahoo.com>
Subject: Re: Having every daemon put itself into the background is bad software
 design
Date: Fri, 06 Dec 2013 09:11:30 -0600
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2013 15:11:36 -0000

On Tue, Dec 3, 2013, at 11:38, Unga wrote:
> 
> Btw, I got in to this problem by trying to use DJB's daemontools to
> supervise my server running on FreeBSD. But it creates zombie processes
> and spawn quite fast. In my daemons, after fork(2), parent returns.
> 

Our own /usr/sbin/daemon utility has the ability to supervise processes
as well, but doesn't respawn processes at an insane rate like
daemontools does. I've seen a coredumping process supervised by
daemontools actually take a server down because of the CPU load.... our
own daemon utility respawns it after waiting 1 second.