From owner-freebsd-stable Fri Oct 16 10:05:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24246 for freebsd-stable-outgoing; Fri, 16 Oct 1998 10:05:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rrnet.com (rrnet.com [206.11.160.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24240 for ; Fri, 16 Oct 1998 10:05:11 -0700 (PDT) (envelope-from freebsdstable@rrnet.com) Received: (from freebsdstable@localhost) by rrnet.com (8.8.8/8.8.8) id MAA25067 for freebsd-stable@FreeBSD.ORG; Fri, 16 Oct 1998 12:04:55 -0500 (CDT) From: Chad Dubuque Message-Id: <199810161704.MAA25067@rrnet.com> Subject: Re: syslogd and syslog.conf To: freebsd-stable@FreeBSD.ORG Date: Fri, 16 Oct 1998 12:04:54 -0500 (CDT) In-Reply-To: from "Randy Bush" at Oct 16, 98 08:25:16 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > > there are potentially non-system routines that will break with this "fix". > > this is the point that worries me. a change is being proposed in a data > file, and it is being assumed that syslogd(8) is the only program which > reads that file. as syslog.conf(5) has been documented publicly, i would be > more cautious about changing the definition, for mere cosmetic not emergency > reasons, without widely published warning well in advance. Y'know, I'm all for documenting a change, but I think your worries are a little unnecessary. For one, the only change being proposed is that spaces will be allowed instead of just tabs. That's it. Heck, I think it makes a lot of sense. BSDI's syslogd understands tabs&/or spaces as whitespace, why shouldn't FreeBSD's? It's not going to add a lot of code, and IT WILL NOT BREAK ANYTHING. However, if you *then* put spaces in your syslog.conf, it may break something (I don't know what) that also reads it. If so, the administrator should realize that (s)he just changed his/her syslog.conf, and change the faulty parser. (Switch to perl, use "\s+".) In short, I believe that syslogd only understanding spaces is a BUG, and that any program that depends on WHITESPACE being only TABS is BROKEN. Fix syslogd, add a paragraph to the man page, put a warning in syslog.conf, and let's get on to fixing other software and writing other drivers. -- Chad Dubuque cdubuque@rrnet.com Fargo, N.D. (USA) Red River Net - Internet Communications http://www.rrnet.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message