Should have just left it alone!

After many months of just running along in the background I recently decided to write a little lua script. No doubt due to my poor programming it was leaking memory and eventually caused the inevitable crash :-(

Before I had realised what the problem was I had tried to edit the cron and the lack of memory caused my cron file to be overwritten with a blank file. I've recovered the cron file but I am having trouble re-connecting the cron file with it's link in the /var/spool/cron/crontabs directory.

Member for

16 years 10 months

brett

9 years 1 month ago

Alan,

The correct way to edit the crontab file is to invoke "crontab -e" this will fire up an editor and do the work once you exit the editor to get it in place.

Brett

Member for

15 years 1 month

allanayr

9 years 1 month ago

Brett

Thanks for this, I do invoke crontab -e to edit the cron file. The permissions on the /var/spool/cron/crontabs/root file are -rw------- I take it that it's not really an issue?

Allan

Member for

16 years 10 months

brett

9 years 1 month ago

Not a problem at all as the "cron" daemon run as root so it can read this.  In anycase it has u+rw access and the file will be owned by root.
Brett

Member for

15 years 1 month

allanayr

9 years 1 month ago

All good then.

It's still a great system!

Thanks