From owner-freebsd-questions@FreeBSD.ORG Mon Mar 28 10:14:38 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F413A16A4D0 for ; Mon, 28 Mar 2005 10:14:37 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0018C43D2D for ; Mon, 28 Mar 2005 10:14:36 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from bsdbox.farid-hajji.net (bsdbox [192.168.254.3]) by fw.farid-hajji.net (Postfix) with ESMTP id 962E84BB18; Mon, 28 Mar 2005 12:14:43 +0200 (CEST) Date: Mon, 28 Mar 2005 12:15:36 +0200 From: cpghost@cordula.ws To: Gert Cuykens Message-ID: <20050328101536.GA620@bsdbox.farid-hajji.net> References: <20050327190511.GB15898@fw.farid-hajji.net> <6.2.0.14.0.20050327142159.03cc89f0@mail.face2interface.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: Marty Landman cc: freebsd-questions@freebsd.org Subject: Re: inetd vs standalone daemon X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2005 10:14:38 -0000 On Sun, Mar 27, 2005 at 09:51:54PM +0200, Gert Cuykens wrote: > > On Sun, Mar 27, 2005 at 07:46:09PM +0200, Gert Cuykens wrote: > > > Can i delete inetd ? > > > > No. With inetd, you can also turn regular filters into network > > aware programs (sort of). And not every network service is always > > needed all the time. Having a deamon for each of those seldom used > > services hanging around is just wastful. > > i think its less wasteful cpu time to run separate daemons then to run > 1 big daemon. Because the big daemon needs to find out which service > it needs to start every time a fedex guy is knocking at the door while > a separate daemon already knows what it needs to do before the fedex > guy is standing at the door. inetd itself is not "big." It doesn't contain all other daemons. Rather than that, it listens on the ports that are configured in /etc/inetd.conf and accepts connections. Then (and only then) would it fork() the configured program to handle the connection. inetd is not useful to every kind of application. Running a web server from inetd for every connection attempt would be silly. But running some obscure service, that is only needed every now and then, could be a good idea. Consider tftp as an example: this is mainly used to netboot diskless machines or to upload IOS updates to routers etc... On a typical network, tftp requests would probably arrive at a rate of <1 per day. Having tftpd hanging around as a daemon is not needed. -cpghost. -- Cordula's Web. http://www.cordula.ws/