From owner-freebsd-bugs Sun Apr 21 11: 0: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6474437B405 for ; Sun, 21 Apr 2002 11:00:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3LI03d21510; Sun, 21 Apr 2002 11:00:03 -0700 (PDT) (envelope-from gnats) Date: Sun, 21 Apr 2002 11:00:03 -0700 (PDT) Message-Id: <200204211800.g3LI03d21510@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: bin/37163: syslogd "#!" feature is misleading/can induce unwanted results. Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/37163; it has been noted by GNATS. From: David Malone To: Jeremy Chadwick Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/37163: syslogd "#!" feature is misleading/can induce unwanted results. Date: Sun, 21 Apr 2002 18:58:48 +0100 On Tue, Apr 16, 2002 at 04:32:13PM -0700, Jeremy Chadwick wrote: > >Description: > syslogd(8) has a particular "feature" which I feel should be disabled by default. This feature is documented, but due to the obfuscated nature of the syslog.conf(5) manpage, most system administrators would probably miss this. Rather than change the behaviour of syslogd and upset people who expect it to work this way, maybe we could edither improve the man page or include a comment in the default syslog.conf warning people about this feature? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message