Re: log file rotation
That was the problem. I fixed the $T00 to @T00 and it works like a charm now. I don't know how that got in there to begin with. It has been working fine. Anyway, thanks and cheers. Jason On Tue, 2006-01-17 at 15:15 -0500, Garance A Drosehn wrote: At 9:23 AM -0600 1/17/06, Jason King wrote: On Tue, 2006-01-17 at 09:16 -0600, David Kelly wrote: On Tue, Jan 17, 2006 at 07:23:25AM -0600, Jason King wrote: Hmm, when I run newsyslog I get the following message: [EMAIL PROTECTED] newsyslog -vv newsyslog: malformed 'at' value: /var/log/clamd.log 640 3 *$T00 BJ /var/run/clamd.pid 1 Any ideas? Use @T00 rather than $T00 It is already @T00. I don't know why it appears as a $ in the email. Just did a copy paste. Go figure on that one. Any other thoughts? If newsyslog is saying that's a bad 'at' value, then there is *something* wrong with that line. Maybe there's some non-printing character in it, which might be why we see $T00 instead of @T00. But as long as newsyslog thinks there is something wrong with the 'at' value on that line, then it will not rotate the files. Maybe you have multiple lines for the same logfile, one with $T00 and one with @T00. Also, you don't need to specify the '1' at the end, since that is just SIGHUP, and newsyslog defaults to using SIGHUP unless you give it some other value. Including the '1' should not cause any problem, though. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
The only thing that was different was on my maillog line the end of the line had only J instead of JC. I'll add that and see if that makes any difference. Thanks, Jason On Mon, 2006-01-16 at 13:27 -0800, Dan O'Connor wrote: My maillog and daillog files have stopped rotating everyday like they use to. I have 2 FBSD machines that have stopped these files from rotating as of Dec 15th. I have no idea what could have caused two different machines to have the same thing happen to them. The entry in my newsyslog.conf file is correct. There is no reason these files shouldn't be rotating daily like before. Anyone have any ideas on what to look for? Only thing I can think of is to check /etc/newsyslog.conf and make sure the lines /var/log/daily.log 640 7 *@T00 JN /var/log/maillog640 7 *@T00 JC are still there. ~Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
Hmm, when I run newsyslog I get the following message: [EMAIL PROTECTED] newsyslog -vv newsyslog: malformed 'at' value: /var/log/clamd.log 640 3 *$T00 BJ /var/run/clamd.pid 1 Any ideas? On Mon, 2006-01-16 at 15:48 -0600, David Kelly wrote: On Mon, Jan 16, 2006 at 02:50:16PM -0600, Jason King wrote: My maillog and daillog files have stopped rotating everyday like they use to. I have 2 FBSD machines that have stopped these files from rotating as of Dec 15th. I have no idea what could have caused two different machines to have the same thing happen to them. The entry in my newsyslog.conf file is correct. There is no reason these files shouldn't be rotating daily like before. Anyone have any ideas on what to look for? Try running newsyslog manually. If that works then its supposed to be run every hour on the hour out of /etc/crontab. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
On Tue, Jan 17, 2006 at 07:23:25AM -0600, Jason King wrote: Hmm, when I run newsyslog I get the following message: [EMAIL PROTECTED] newsyslog -vv newsyslog: malformed 'at' value: /var/log/clamd.log 640 3 *$T00 BJ /var/run/clamd.pid 1 Any ideas? Use @T00 rather than $T00 -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
It is already @T00. I don't know why it appears as a $ in the email. Just did a copy paste. Go figure on that one. Any other thoughts? On Tue, 2006-01-17 at 09:16 -0600, David Kelly wrote: On Tue, Jan 17, 2006 at 07:23:25AM -0600, Jason King wrote: Hmm, when I run newsyslog I get the following message: [EMAIL PROTECTED] newsyslog -vv newsyslog: malformed 'at' value: /var/log/clamd.log 640 3 *$T00 BJ /var/run/clamd.pid 1 Any ideas? Use @T00 rather than $T00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
On Tue, Jan 17, 2006 at 09:23:31AM -0600, Jason King wrote: It is already @T00. I don't know why it appears as a $ in the email. Just did a copy paste. Go figure on that one. Any other thoughts? Your error is malformed at value and when one does copy/paste the data appears differently than expected. Therefore there is something wrong with the way its typed, maybe high bit set on one or more characters. Suggest deleting the * up to the BJ and retype with care. Retry. On Tue, 2006-01-17 at 09:16 -0600, David Kelly wrote: On Tue, Jan 17, 2006 at 07:23:25AM -0600, Jason King wrote: Hmm, when I run newsyslog I get the following message: [EMAIL PROTECTED] newsyslog -vv newsyslog: malformed 'at' value: /var/log/clamd.log 640 3 *$T00 BJ /var/run/clamd.pid 1 Any ideas? Use @T00 rather than $T00 -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
On Tue, Jan 17, 2006 at 09:41:29AM -0600, David Kelly wrote: On Tue, Jan 17, 2006 at 09:23:31AM -0600, Jason King wrote: It is already @T00. I don't know why it appears as a $ in the email. Just did a copy paste. Go figure on that one. Any other thoughts? Your error is malformed at value and when one does copy/paste the data appears differently than expected. Therefore there is something wrong with the way its typed, maybe high bit set on one or more characters. Suggest deleting the * up to the BJ and retype with care. Retry. For fun try hexdump -C /etc/newsyslog.conf | more to see exactly what is typed. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
At 9:23 AM -0600 1/17/06, Jason King wrote: On Tue, 2006-01-17 at 09:16 -0600, David Kelly wrote: On Tue, Jan 17, 2006 at 07:23:25AM -0600, Jason King wrote: Hmm, when I run newsyslog I get the following message: [EMAIL PROTECTED] newsyslog -vv newsyslog: malformed 'at' value: /var/log/clamd.log 640 3 *$T00 BJ /var/run/clamd.pid 1 Any ideas? Use @T00 rather than $T00 It is already @T00. I don't know why it appears as a $ in the email. Just did a copy paste. Go figure on that one. Any other thoughts? If newsyslog is saying that's a bad 'at' value, then there is *something* wrong with that line. Maybe there's some non-printing character in it, which might be why we see $T00 instead of @T00. But as long as newsyslog thinks there is something wrong with the 'at' value on that line, then it will not rotate the files. Maybe you have multiple lines for the same logfile, one with $T00 and one with @T00. Also, you don't need to specify the '1' at the end, since that is just SIGHUP, and newsyslog defaults to using SIGHUP unless you give it some other value. Including the '1' should not cause any problem, though. -- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute; Troy, NY; USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
log file rotation
My maillog and daillog files have stopped rotating everyday like they use to. I have 2 FBSD machines that have stopped these files from rotating as of Dec 15th. I have no idea what could have caused two different machines to have the same thing happen to them. The entry in my newsyslog.conf file is correct. There is no reason these files shouldn't be rotating daily like before. Anyone have any ideas on what to look for? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
My maillog and daillog files have stopped rotating everyday like they use to. I have 2 FBSD machines that have stopped these files from rotating as of Dec 15th. I have no idea what could have caused two different machines to have the same thing happen to them. The entry in my newsyslog.conf file is correct. There is no reason these files shouldn't be rotating daily like before. Anyone have any ideas on what to look for? Only thing I can think of is to check /etc/newsyslog.conf and make sure the lines /var/log/daily.log 640 7 *@T00 JN /var/log/maillog640 7 *@T00 JC are still there. ~Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
On Mon, Jan 16, 2006 at 02:50:16PM -0600, Jason King wrote: My maillog and daillog files have stopped rotating everyday like they use to. I have 2 FBSD machines that have stopped these files from rotating as of Dec 15th. I have no idea what could have caused two different machines to have the same thing happen to them. The entry in my newsyslog.conf file is correct. There is no reason these files shouldn't be rotating daily like before. Anyone have any ideas on what to look for? Try running newsyslog manually. If that works then its supposed to be run every hour on the hour out of /etc/crontab. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: log file rotation
At 2:50 PM -0600 1/16/06, Jason King wrote: My maillog and daillog files have stopped rotating everyday like they use to. I have 2 FBSD machines that have stopped these files from rotating as of Dec 15th. I have no idea what could have caused two different machines to have the same thing happen to them. The entry in my newsyslog.conf file is correct. There is no reason these files shouldn't be rotating daily like before. Anyone have any ideas on what to look for? Check timestamps on the various files. perhaps some kind of timewarp happened. Check to make sure newsyslog is still being run from cron. (do you have other files which are rotating, but just those two are not rotating?) Run:newsyslog -vv and see if it tells you anything interesting. -- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute; Troy, NY; USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
