Date: Tue, 3 Oct 2000 23:49:56 -0200 From: "Mario Sergio Fujikawa Ferreira" <lioux@uol.com.br> To: Brian Somers <brian@Awfulhak.org> Cc: Mario Sergio Fujikawa Ferreira <lioux@uol.com.br>, freebsd-stable@FreeBSD.ORG Subject: Re: newsyslog.conf error on latest stable? Message-ID: <20001003234956.A1366@Fedaykin.here> In-Reply-To: <200010040049.e940nOs36506@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Oct 04, 2000 at 01:49:02AM %2B0100 References: <lioux@uol.com.br> <200010040049.e940nOs36506@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 04, 2000 at 01:49:02AM +0100, Brian Somers wrote: > > This really sounds like you haven't got version 1.25.2.1 of > newsyslog.c installed.... This was when the above format was added > and was committed to -stable on May 19. I am positive that I using the latest versions, but... MD5 (newsyslog.c) = c2f8b0b7543a1312bd178957fe7fd00c MD5 (pathnames.h) = 741be923233db85fec663603752189ab I was worried about a typo inside newsyslog.conf but everthing seems to check with what newsyslog(8) expects. Besides, I am using a -STABLE shipped newsyslog.conf file to be sure this is not a typo. At least, not mine. :) > Having said that, I would have thought you should be seeing a > ``malformed interval'' message if you had an old newsyslog, so the > only other thing I can think of is that you've got something dodgy in > your newsyslog.conf.... what do you see if you ``cat -vet > newsyslog.conf'' ? I get the following. I was assuming this as correct since the md5 for /usr/src/etc/newsyslog.conf and /etc/newsyslog.conf are identical. MD5 (/etc/newsyslog.conf) = 716810f8e00a9175e7886e27b7facad8 MD5 (/usr/etc/etc/newsyslog.conf) = 716810f8e00a9175e7886e27b7facad8 The `cat -vet` output is: # configuration file for newsyslog$ # $FreeBSD: src/etc/newsyslog.conf,v 1.25.2.2 2000/09/20 02:43:46 jkh Exp $$ #$ # logfilename [owner:group] mode count size when [ZB] [/pid_file] [sig_num]$ /var/log/cron^I^I^I^I600 3^I 100 * Z$ /var/log/amd.log^I^I^I644 7^I 100 * Z$ /var/log/kerberos.log^I^I^I644 7^I 100 * Z$ /var/log/lpd-errs^I^I^I644 7^I 100 * Z$ /var/log/maillog^I^I^I644 7 * @T00 Z$ /var/log/sendmail.st^I^I^I644 10 * 168 B$ /var/log/messages^I^I^I644 5^I 100 * Z$ /var/log/all.log^I^I^I600 7 * @T00 Z$ /var/log/slip.log^I^I^I600 3^I 100 * Z$ /var/log/ppp.log^I^I^I600 3^I 100^I* Z$ /var/log/security^I^I^I600 10 100 * Z$ /var/log/wtmp^I^I^I^I644 3^I *^I@01T05 B$ /var/log/daily.log^I^I^I640 7 * @T00 Z$ /var/log/weekly.log^I^I^I640 5 1 $W6D0 Z$ /var/log/monthly.log^I^I^I640 12 * $M1D0 Z$ I can't seem to identify the problem. I've just erased both /usr/src/etc/newsyslog.conf and /usr/src/usr.sbin/newsyslog. Let's see what cvsup brings me tonight. Odd. -- Mario S. F. Ferreira - UnB - Brazil - "I guess this is a signature." lioux at ( freebsd dot org | linf dot unb dot br ) flames to beloved devnull@someotherworldbeloworabove.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001003234956.A1366>