From owner-freebsd-security Sun Sep 13 10:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21338 for freebsd-security-outgoing; Sun, 13 Sep 1998 10:17:19 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from phluffy.lm.com (phluffy.lm.com [204.171.44.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21333 for ; Sun, 13 Sep 1998 10:17:17 -0700 (PDT) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.lm.com (8.9.0/8.8.8) with ESMTP id NAA27678; Sun, 13 Sep 1998 13:16:44 -0400 (EDT) (envelope-from myke@ees.com) Date: Sun, 13 Sep 1998 13:16:43 -0400 (EDT) From: Mike Holling X-Sender: myke@phluffy.lm.com To: sthaug@nethelp.no cc: marquis@roble.com, freebsd-security@FreeBSD.ORG Subject: Re: sshd In-Reply-To: <20632.905676426@verdi.nethelp.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > If you're running inetd then it doesn't seem consistent to start > > daemons that don't need to run all the time from startup scripts. > > Inetd was designed to conserve memory. If you have it why not use it? > > /etc/inetd.conf is also a common place to implement access control (via > > tcp_wrappers). Inetd runs many things, and on some of the (older) machines here inetd occasionally dies. It's very nice to have ssh run standalone so you can still get into the machine remotely and restart inetd. - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message