Date: Tue, 6 Oct 1998 10:27:06 +0200 From: Philippe Regnauld <regnauld@deepo.prosa.dk> To: brooks@one-eyed-alien.net Cc: security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <19981006102706.39881@deepo.prosa.dk> In-Reply-To: <Pine.SOL.4.02.9810051054550.24223-100000@orion.ac.hmc.edu>; from brooks@one-eyed-alien.net on Mon, Oct 05, 1998 at 10:59:28AM -0700 References: <4.1.19981005093222.041901f0@mail.lariat.org> <Pine.SOL.4.02.9810051054550.24223-100000@orion.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
brooks@one-eyed-alien.net writes: > On Mon, 5 Oct 1998, Brett Glass wrote: > > being the same as spaces in sendmail.cf and Makefiles. One thing you can > do in this case is use a sanity checker for syslog.conf files like the one > I wrote. You can get it at: > > http://www3.hmc.edu/~brdavis/software/syslogck/ One thing that could be done was to have a wrapper (like crontab -e) that checked syntax (f.ex, with your script) before installing the syslog.conf ? The wrapper would complain noisily and refuse to let you save the file if the file was bogus. syslog -e ? :-) -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. 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?19981006102706.39881>