From owner-freebsd-security Wed Sep 6 13:21:32 1995 Return-Path: security-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.11/8.6.6) id NAA19638 for security-outgoing; Wed, 6 Sep 1995 13:21:32 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.11/8.6.6) with ESMTP id NAA19619 for ; Wed, 6 Sep 1995 13:21:28 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id NAA13308; Wed, 6 Sep 1995 13:20:19 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA26565; Wed, 6 Sep 1995 13:22:16 -0700 Message-Id: <199509062022.NAA26565@corbin.Root.COM> To: Tom Samplonius cc: Bill Trost , Brian Tao , freebsd-security@freebsd.org Subject: Re: Do we *really* need logger(1)? In-reply-to: Your message of "Wed, 06 Sep 95 12:56:23 PDT." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 06 Sep 1995 13:22:14 -0700 Sender: security-owner@freebsd.org Precedence: bulk >On Wed, 6 Sep 1995, Bill Trost wrote: > >> Internet, so syslogd(8) can also be used as a remote disk-filling >> service. (And, since it's UDP-based, you can't tcp-wrap it...). > > tcp_wrapper is primitive. xinetd is better and can support UDP. Um, syslogd is a daemon and is not spawned by inetd...so how would doing anything with inetd affect this problem? -DG