From owner-freebsd-stable Fri Oct 16 08:25:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10454 for freebsd-stable-outgoing; Fri, 16 Oct 1998 08:25:39 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10449 for ; Fri, 16 Oct 1998 08:25:38 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (752 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Fri, 16 Oct 1998 08:25:16 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Fri, 16 Oct 1998 08:25:16 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Clark Gaylord Cc: freebsd-stable@FreeBSD.ORG Subject: Re: syslogd and syslog.conf Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message