From owner-freebsd-bugs Fri Jan 14 6:57:40 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 5831B14CE1; Fri, 14 Jan 2000 06:57:36 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DC8F71CA0; Fri, 14 Jan 2000 22:57:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Dag-Erling Smorgrav Cc: billf@FreeBSD.ORG, pekkas@netcore.fi, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/15414: syslogd -ss disables all network logging functions In-Reply-To: Message from Dag-Erling Smorgrav of "14 Jan 2000 15:27:06 +0100." Date: Fri, 14 Jan 2000 22:57:33 +0800 From: Peter Wemm Message-Id: <20000114145733.DC8F71CA0@overcee.netplex.com.au> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling Smorgrav wrote: > writes: > > Synopsis: syslogd -ss disables all network logging functions [..] > If syslogd is started with -ss, it will not be able to log to a remote > machine because -ss instructs it to not open an UDP socket at all. > > What the originator really wants is -s, which instructs syslogd to > open a socket but only use it for *sending* log messages. Incomig > messages will be logged and discarded. One could argue that syslogd > should not even bother with that, but it *has* to bind the socket > because the receiving end will reject packets which do not originate > from port 514, and there is no way to make the socket write-only > (except maybe setting the receive buffer size to 0... I'll have to try > that). Or 'open(); bind(); sendto(); close()' for each remote message.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message