-
Yes the gz file times are off because I ended up putting in another cron entry to re-run the cron30min script to force the first cron30min script to end. that way I get something generated in a timely manner.
Here is the output of ps -ef | grep ipaudit
[root@monitor ~]# ps -ef | grep ipaudit
root 682 653 0 08:15 pts/1 00:00:00 grep ipaudit
ipaudit 32343 2312 0 08:05 ?.
2009-03-18 14:04:42 UTC in ipaudit
-
Yes the gz file times are off because I ended up putting in another cron entry to re-run the cron30min script to force the first cron30min script to end. that way I get something generated in a timely manner.
Here is the output of ps -ef | grep ipaudit
[root@monitor ~]# ps -ef | grep ipaudit
root 682 653 0 08:15 pts/1 00:00:00 grep ipaudit
ipaudit 32343 2312 0 08:05 ?.
2009-03-18 12:41:43 UTC in ipaudit
-
[root@monitor 30min]# pwd
/home/ipaudit/data/30min
[root@monitor 30min]# ls -lt | head -10
total 126000
-rw-r--r-- 1 ipaudit ipaudit 40406 2009-03-16 11:35 2009-03-16-11:30.txt.gz
-rw-r--r-- 1 root ipaudit 931927 2009-03-16 11:30 2009-03-16-11:00.txt
-rw-r--r-- 1 ipaudit ipaudit 45523 2009-03-16 11:05 2009-03-16-11:00.txt.gz
-rw-r--r-- 1 root ipaudit 907670 2009-03-16 11:00...
2009-03-16 15:48:41 UTC in ipaudit
-
I've searched through the past posts for a solution to this and have seen similar problems, but no real solution. I am using a 32bit Fedora Core 8 server running ipaudit. I have gnuplot 4.2 patch level 2, tcpdump version 3.9.7, libpcap version 0.9.7 and gzip version 1.3.12.
I am having a problem with the cron30min scripts completing. Essentially, the 30min script runs and collects data, but...
2009-03-13 17:06:27 UTC in ipaudit
