Greg, I believe the problem has already been solved thanks to some help from a gentleman who sent me some information privately.
I won't know for certain for a day or two but I am optimistic. I want to thank the people who responded with some suggestions for debugging and things to try. I'm going to unsubscribe from the list now. Nobody was able to tell me how to replace the functionality of the " */10 * * * * /usr/libexec/atrun" line in my cron file. I had read the man pages regarding "at" before I asked the question but I didn't fully understand how "at" might replace atrun. So if someone cares to help on that last question please shoot me a private email. Have a great day everyone. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Greg Thomas > Sent: Thursday, June 30, 2005 2:38 PM > To: [email protected] > Subject: Re: DOS Attacks? > > If you're really interested in discovering the cause then you'd > refrain from wasting time justifying your troubleshooting approach and > start providing useful information. As Jason said, it could be > anything, even a DOS attack, but without info no one is going to be > able to help even if it is a DOS attack. Does that really help? > > Greg
