From owner-freebsd-bugs  Thu Jan 30 12:40:06 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA29813
          for bugs-outgoing; Thu, 30 Jan 1997 12:40:06 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA29795;
          Thu, 30 Jan 1997 12:40:04 -0800 (PST)
Resent-Date: Thu, 30 Jan 1997 12:40:04 -0800 (PST)
Resent-Message-Id: <199701302040.MAA29795@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, dlowe@sirius.com
Received: from news3.sirius.com (news3.sirius.com [205.134.226.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA29541
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 30 Jan 1997 12:35:14 -0800 (PST)
Received: (from root@localhost)
	by news3.sirius.com (8.8.5/Sirius-97.01.23) id MAA19289;
	Thu, 30 Jan 1997 12:37:58 -0800 (PST)
Message-Id: <199701302037.MAA19289@news3.sirius.com>
Date: Thu, 30 Jan 1997 12:37:58 -0800 (PST)
From: dlowe@sirius.com
Reply-To: dlowe@sirius.com
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: bin/2622: syslogd '-s' behavior either broken or poorly documented
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         2622
>Category:       bin
>Synopsis:       syslogd '-s' behavior either broken or poorly documented
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 30 12:40:02 PST 1997
>Last-Modified:
>Originator:     David Lowe
>Organization:
Sirius Communications
>Release:        FreeBSD 2.2-BETA_A i386
>Environment:

FreeBSD 2.2-BETA running 'syslogd -s' and attempting to log to a Solaris
2.5.1 machine.

>Description:

This may be either a problem with syslogd, or a problem with the syslogd
man page.  Running syslogd with the '-s' switch disables incoming *and*
outgoing network syslogs, whereas the man page says:

---
 -s	Operate in secure mode.  Do not open a UDP socket to listen for
	log message from remote machines.
---

When run with this switch, however, syslogd also won't open a UDP socket to
send log messages, and (as far as I could tell) generates no explanation or
debugging output.

>How-To-Repeat:

on client machine:

	run syslogd with -s
	add a 'facility.level		@loghost' line to your /etc/syslog.conf
	logger -p user.crit testing syslogd -s

on log host:

	syslogd should be running (without -s)
	check logs.. nothing!

>Fix:
	
Workaround by running syslogd without -s on client machines.

Fix by either updating the man page so I don't tear my hair out all morning
trying to figure out why it's broken, or updating the code so -s does what
it says it's going to.

>Audit-Trail:
>Unformatted: