Press "Enter" to skip to content

cron jobs on

As you may have noticed has been slow to nonresponsive today.
Part of the problem was old cron jobs that were still running. Rather
than trying to figure out which are valid and which are not. I copied the
crontab file to your account with the name cron.bck.2008.06.05 and removed
the cron.

If your cronjob needs to run, you’ll need to set it up again. I do ask
however that you try to refrain from running the job every minute

In addition to the cronjobs using a large percentage of the cpu, a few
outside IPs were spamming the server with requests. We’ve started banning
ips and I’m now looking into what exactly they were trying to access.

Nancy D. Lewis
ITP: 212-998-9170