From nobody@FreeBSD.ORG  Sat Dec 11 01:02:42 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 80CAB14F66; Sat, 11 Dec 1999 01:01:59 -0800 (PST)
Message-Id: <19991211090159.80CAB14F66@hub.freebsd.org>
Date: Sat, 11 Dec 1999 01:01:59 -0800 (PST)
From: pekkas@netcore.fi
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: syslogd -ss disables all network logging functions
X-Send-Pr-Version: www-1.0

>Number:         15414
>Category:       bin
>Synopsis:       syslogd -ss disables all network logging functions
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Dec 11 01:10:01 PST 1999
>Closed-Date:    Fri Jan 14 06:08:10 PST 2000
>Last-Modified:  Fri Jan 14 06:11:23 PST 2000
>Originator:     Pekka Savola
>Release:        3.4-RC, 3.3-RELEASE
>Organization:
>Environment:
FreeBSD blah.here 3.4-RC FreeBSD 3.4-RC #0: Sat Dec 11 03:33:19 EET 1999     root@blah.here:/usr/src/sys/compile/MYKERNEL  i386
>Description:
syslogd -ss disables all network functions; you can't even log on
to remote syslogd's anymore.  

This probably should be so that syslogd doesn't start listening on
syslogd port (netstat -a).

If this isn't the case, there IMO should be some kind of "--nolisten" 
option as in GNU/Linux syslogds.
>How-To-Repeat:
Start syslogd with -ss and put a line like this in syslogd.conf:

*.* @myother.host

>Fix:


>Release-Note:
>Audit-Trail:
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 

thanks. 
State-Changed-From-To: feedback->closed 
State-Changed-By: des 
State-Changed-When: Fri Jan 14 06:08:10 PST 2000 
State-Changed-Why:  
This is not a bug, though one may argue that the man page is slightly 
imprecise. Suggest the originator read the man page closely. 
>Unformatted:
