Date: Tue, 11 Feb 2003 14:30:03 -0800 From: Wesley Peters <wes@softweyr.com> To: Thomas Quinot <thomas@freebsd.org>, arch@freebsd.org Subject: Re: syslog.conf syntax change (multiple program/host specifications) Message-ID: <200302111430.03156.wes@softweyr.com> In-Reply-To: <20030210114930.GB90800@melusine.cuivre.fr.eu.org> References: <20030210114930.GB90800@melusine.cuivre.fr.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 10 February 2003 03:49, Thomas Quinot wrote: > I'm about to commit a change to syslogd to allow multiple hosts or > programs to be named in program or host specifications, eg: > > !foo,bar > *.* /var/log/only_foo_or_bar.log > > !-foo,bar > *.* /var/log/all_except_foo_or_bar.log > > Any objections to this change? A patch is available for > review at http://www.cuivre.fr.eu.org/~thomas/syslogd.c.diff. Excellent. I have another simple change to syslog I want to cast before the audience for consideration. I have an embedded platform that needs to not run the log partition out of disk space. We've encountered problems at a few very busy customer sites where something will babble into syslog faster than newsyslog can keep up. I've made the following change to syslogd and syslog.conf accomodate our needs: ... auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog G 4M lpr.info /var/log/lpd-errs 256K local3.* /var/log/foo B 1K ftp.* /var/log/ftp B 1M cron.* /var/log/cron ... Each line, after the filename, can specify a logfile size limit and an optional disposition. The size limit should be self explanatory, size scalars of K through E plus B for blocks are supported. The optional disposition can be 'M' for Max file size, the existing logfile is renamed with a .bak extension and a new one created; 'B' or 'G' for bzip2 or gzip the file and create a new one, or 'R' to simply remove and recreate the file. The implied operation is 'M' if none is specified, as in the lpr.info line above. This mod has been running on my 4.7R workstation for a month now, and on a (4.4 + security fixes) appliance in our test lab as well. We've noticed no problems. Attached is a diff against 4.7R. If anyone at all is interested in this I'll provide a patch against -CURRENT as soon as I get my -CURRENT machine up at home. Anyone who thinks this is dumb or unneeded should let me know sooner rather than later. On a side note, this is the first of what we hope will be many small and hopefully larger transfers of functionality from ${DAY_JOB} to FreeBSD. 'tis a good place I've landed, aye. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302111430.03156.wes>