Date: Wed, 2 Oct 2002 10:27:04 -0700 (PDT) From: Tuc <freebsd@ttsg.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/43594: syslog.conf with #! in start prevents other rules from running Message-ID: <200210021727.g92HR4WV051215@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 43594
>Category: bin
>Synopsis: syslog.conf with #! in start prevents other rules from running
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Oct 02 10:30:04 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Tuc
>Release: 4.6
>Organization:
TTSG Internet Services, Inc.
>Environment:
FreeBSD himinbjorg.ttsg.com 4.6-RC FreeBSD 4.6-RC #4: Thu Aug 8 10:56:19 EDT 2002 root@himinbjorg.ttsg.com:/usr/src/sys/compile/HIMINBJORG i386
>Description:
When we put an entry in /etc/syslog.conf, after commenting the rest of
it out, syslog won't log to those new entries
>How-To-Repeat:
Add :
#!startslip
#*.* /var/log/slip.log
#!ppp
#*.* /var/log/ppp.log
To /etc/syslog.conf, and notice it won't do anything. Now do :
*.* /var/log/spool
*.* /var/log/spool2
#!startslip
#*.* /var/log/slip.log
#!ppp
#*.* /var/log/ppp.log
HUP syslog, and it'll log to the files.
Now do :
#!startslip
#*.* /var/log/slip.log
#!ppp
#*.* /var/log/ppp.log
*.* /var/log/spool
*.* /var/log/spool2
HUP syslog. Now it won't log to the files.
>Fix:
N/A
>Release-Note:
>Audit-Trail:
>Unformatted:
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?200210021727.g92HR4WV051215>