Re: log file rotation

2006-01-23 Thread Jason King
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: > >

Re: log file rotation

2006-01-17 Thread Garance A Drosehn
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: >

Re: log file rotation

2006-01-17 Thread David Kelly
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

Re: log file rotation

2006-01-17 Thread David Kelly
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 e

Re: log file rotation

2006-01-17 Thread Jason King
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 followi

Re: log file rotation

2006-01-17 Thread David Kelly
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?

Re: log file rotation

2006-01-17 Thread Jason King
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 a

Re: log file rotation

2006-01-17 Thread Jason King
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

Re: log file rotation

2006-01-16 Thread Garance A Drosehn
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 t

Re: log file rotation

2006-01-16 Thread David Kelly
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 t

Re: log file rotation

2006-01-16 Thread Dan O'Connor
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 i

log file rotation

2006-01-16 Thread Jason King
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