From owner-freebsd-security Wed Oct 7 08:40:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13891 for freebsd-security-outgoing; Wed, 7 Oct 1998 08:40:50 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13853 for ; Wed, 7 Oct 1998 08:40:42 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id IAA03931; Wed, 7 Oct 1998 08:40:36 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdaX3922; Wed Oct 7 08:40:00 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id IAA01822; Wed, 7 Oct 1998 08:39:49 -0700 (PDT) Message-Id: <199810071539.IAA01822@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdrR1818; Wed Oct 7 08:39:43 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Brett Glass cc: "Jeffrey J. Mountin" , Dan Busarow , Studded , freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) In-reply-to: Your message of "Tue, 06 Oct 1998 21:35:12 MDT." <4.1.19981006213234.04cd1600@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 08:39:34 -0700 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In the name of consistency, I'd like to see FreeBSD (and, for that matter, > ALL the BSDs) treat tabs and spaces the same, letting you quote spaces with > a backslash (or quotes surrounding a string) if you want to embed them. I've been caught by this many times. Add to the list Solaris, HP-UX, DEC UNIX, AIX, Linux, ... One would think that with every UN*X operating system having this "feature", syslogd's use of tabs instead of spaces would be common knowledge. Granted, a newbie would not know this, however I remember the first time I made this mistake I remembered not to make it again. On the other hand it could be argued that FreeBSD should a more tolerant syslogd. This would cause the FreeBSD syslogd to be incompatible with other syslogd's, meaning I could create a syslogd for my shop (Suns, Alphas, RS/6000's, DG boxes, HP boxes, Linux boxes, and FreeBSD boxes). If FreeBSD were to have a different syslogd I would not be able to copy my syslogd.conf or cat any additions to any syslogd.conf file. I would have one master file for FreeBSD and another for the other systems. A syslogd.conf syntax checker (as mentioned in an earlier posting) might be a better solution. It could be run at boot or via cron and email its results to the sysadmin. This could be written as a small Perl script. That's my $0.02 worth. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message