Date: Sun, 27 Jun 1999 22:25:11 -0700 From: Aaron Smith <aaron-fbsd@mutex.org> To: John Baldwin <jobaldwi@vt.edu> Cc: Aaron Smith <aaron-fbsd@mutex.org>, Doug <DougGuy@dal.net>, David Malone <dwmalone@maths.tcd.ie>, freebsd-hackers@FreeBSD.ORG, Sheldon Hearn <sheldonh@uunet.co.za> Subject: Re: Inetd and wrapping. Message-ID: <199906280525.WAA48626@sigma.veritas.com> In-Reply-To: Your message of "Sun, 27 Jun 1999 22:26:34 EDT." <199906280226.WAA09596@smtp3.erols.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 27 Jun 1999 22:26:34 EDT, John Baldwin writes: >Let's say I have two services, foo and bar, with food and bard. I want to >wrap food, but *NOT* bard and they are both in /etc/inetd.conf. How do >you propose to solve this with the internal wrapping (which is a good >idea, IMO as it eliminates an exec())? i wouldn't...i'd have to either pay the (small) cost of wrapping or pay the (less small) tcpd exec and not use internal wrapping. it's "nice" to save the exec, but intensely performance or latency sensitive daemons probably shouldn't be starting out of inetd, they should be standalone and preforked or threaded... aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906280525.WAA48626>