Date: 14 Jan 2000 15:27:06 +0100 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: <billf@FreeBSD.ORG> Cc: pekkas@netcore.fi, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/15414: syslogd -ss disables all network logging functions Message-ID: <xzpiu0wohj9.fsf@flood.ping.uio.no> In-Reply-To: <billf@FreeBSD.ORG>'s message of "Thu, 13 Jan 2000 17:47:35 -0800 (PST)" References: <200001140147.RAA23443@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<billf@FreeBSD.ORG> writes: > Synopsis: syslogd -ss disables all network logging functions > > State-Changed-From-To: open->feedback > State-Changed-By: billf > State-Changed-When: Thu Jan 13 17:44:35 PST 2000 > State-Changed-Why: > I can't reproduce this problem, or at least can't understand the bug report. > > Please send actual output that displays the broken behavior to billf@FreeBSD.org 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). DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpiu0wohj9.fsf>