RE: [leaf-user] Shorewall logs

2004-08-18 Thread Chris Lee
Dear David, I see ulogd file at /etc/cron.daily which seems to do the job: -- cchvpn# cat ulogd #!/bin/sh # Save daily LOGDEPTH versions of syslogfile LOGDEPTH=4 # syslogfile name LOGFILE=/var/log/shorewall.log if [ -f $LOGFILE ]; then savelog -g

RE: [leaf-user] Shorewall logs

2004-08-18 Thread David Pitts
University of Western Australia Telephone: (08) 6488 3492 Fax: (08) 6488 1012 -Original Message- From: Chris Lee [mailto:[EMAIL PROTECTED] Sent: Wednesday, 18 August 2004 3:43 PM To: David Pitts; [EMAIL PROTECTED] Subject: RE: [leaf-user] Shorewall logs Dear David, I see ulogd file

RE: [leaf-user] Shorewall logs

2004-08-18 Thread Chris Lee
Dear David, If I run that script manually it works fine, but it doesn't seem to be running automatically. try issue ps command, see if cron is running. 32220 root284 S /usr/sbin/cron hope this help. Regards, Chris Lee ---

Re: [leaf-user] Shorewall logs have bad dates in them

2004-07-27 Thread Tom Eastep
John Desmond wrote: Sorry if this has been covered before. It looks like a real obvious problem, but I'm all Google-eyed from looking for it and couldn't find anything on it. I'm using Shorewall 2.0.2f and the logs always have Dec 31 19:00:00 for the date for REJECTS in the all2all chain. I don't

Re: [leaf-user] Shorewall logs have bad dates in them

2004-07-27 Thread Erich Titl
John At 20:52 27.07.2004, you wrote: John Desmond wrote: Sorry if this has been covered before. It looks like a real obvious problem, but I'm all Google-eyed from looking for it and couldn't find anything on it. I'm using Shorewall 2.0.2f and the logs always have Dec 31 19:00:00 for the date for