This happened to me once. Check how many instances of CRON are running,
by yuping "ps -e | grep cron"
Multiple crons will spawn multiple instances of the script to run at the
same time, which causes the results you have seen.
Regards,
Greg.
Gregg wrote:
>
> ----- Original Message ----- From: "Greg Kuhnert"
> <greg.kuhnert (at mark) theanchoragesylvania.com>
> To: "User Ernie" <ernie (at mark) info.eis.net.au>
> Cc: <coba-e (at mark) bluequartz.org>
> Sent: Friday, January 18, 2008 11:53 PM
> Subject: [coba-e:11742] Re: POP3 DOS attack
>
>
>> Hi Ernie.
>>
>> Have a look at the info at http://www.gregkuhnert.com/public:bq:dfix
>>
>> This offers a few options that may help you out with this problem.
>>
>> Regards,
>> Greg
>>
> Thanks for that link Greg.
>
> I am testing it on my system, and it seems to work nicely.
> There is one little issue I don't know what to do about.
> Every once in a while I get a message in my email with:
> grep: /tmp/badip.good: No such file or directory
> grep: /tmp/badip.good: No such file or directory
>
> I like getting the messages from cron.minutely letting me know that it
> has blocked an ip address, but I would rather not get these error
> messages.
> I don't know why it's even giving an error, because the badip.good
> file does exist.
> Any suggestions?
>
> Gregg.