mkniskanen
Verified User
Hello again,
I have a customer whose account was suspended because an indexing robot was misbehaving and kept reloading the same page for several days and generating several gigabytes of traffic.
Well, it was easy to unsuspend the account and give him a few gigs more so that his pages became visible again. No problem there.
I noticed, however, that the cron job (=crontab) I had written for him had been completely wiped out. At first I thought somebody from the company had been tampering with the settings but looking at the time stamps revealed that auto-suspending the account had done it.
Is there a way to prevent this behaviour?
Markku
I have a customer whose account was suspended because an indexing robot was misbehaving and kept reloading the same page for several days and generating several gigabytes of traffic.
Well, it was easy to unsuspend the account and give him a few gigs more so that his pages became visible again. No problem there.
I noticed, however, that the cron job (=crontab) I had written for him had been completely wiped out. At first I thought somebody from the company had been tampering with the settings but looking at the time stamps revealed that auto-suspending the account had done it.
Is there a way to prevent this behaviour?
Markku