Date: Thu, 08 Oct 1998 01:52:45 -0500 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: Cy Schubert - ITSD Open Systems Group <cschuber@uumail.gov.bc.ca> Cc: freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <3.0.3.32.19981008015245.00feeec4@207.227.119.2> In-Reply-To: <199810071539.IAA01822@cwsys.cwsent.com> References: <Your message of "Tue, 06 Oct 1998 21:35:12 MDT." <4.1.19981006213234.04cd1600@mail.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:39 AM 10/7/98 -0700, Cy Schubert - ITSD Open Systems Group wrote: >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. Consistancy would make administrating various systems easier, but how far could this be taken. I'm being rhetorical, but doing will break additional functionality. As someone that always used tabs in syslog.conf, no difference was known when using Solaris and Irix. <shrug> I did miss the A and B flags in Solaris, among a host of little nags and ps's lack of functionality. Got a kick out of the bsd-like binaries. >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. Best to keep things as similar as possible, so my vote is for the tab. >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. Agreed. Wouldn't awk be a shorter/better way though? Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19981008015245.00feeec4>