Date: Thu, 30 Jan 1997 12:37:58 -0800 (PST) From: dlowe@sirius.com To: FreeBSD-gnats-submit@freebsd.org Subject: bin/2622: syslogd '-s' behavior either broken or poorly documented Message-ID: <199701302037.MAA19289@news3.sirius.com> Resent-Message-ID: <199701302040.MAA29795@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701302037.MAA19289>