Date: Thu, 8 Oct 1998 10:08:32 -0700 (PDT) From: brooks@one-eyed-alien.net To: "Jeffrey J. Mountin" <jeff-ml@mountin.net> Cc: Cy Schubert - ITSD Open Systems Group <cschuber@uumail.gov.bc.ca>, freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <Pine.SOL.4.02.9810081004480.5519-100000@orion.ac.hmc.edu> In-Reply-To: <3.0.3.32.19981008015245.00feeec4@207.227.119.2>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 8 Oct 1998, Jeffrey J. Mountin wrote: > >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? If all you want is syntax checking, probably. However, at least under Solaris, syslog can bite you all sorts of different ways due to the fact that you can't get warnings unless you run it in debug mode. In addition to syntax checking my perl script warns you about thinks like non-existant files (syslog doesn't create files on solaris), non-existant loghsts, and bogus users. It's even got an option to create the necessicary files. I don't think I'd want to go to the effort of doing that in awk. :-) -- Brooks 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?Pine.SOL.4.02.9810081004480.5519-100000>