Get it while it's hot.
Get it while it's hot.
I only recently discovered why it is so dangerous to make crontab -e and crontab -r do such different things and yet be so close together on the US keyboard layout. The first command allows you to edit your cronjobs in your favorite editor, while the second one erases your list of jobs without hesitation.
To prevent this problem, I recommend two things. First, regularly back up your /var/spool/cron/[username] file, which is where this data lives. Second, alias crontab -r to crontab -ri, which prompts to make sure you actually want to do that.
If you're thinking about patching your ssh server or doing something else elaborate or retarded based on Google's suggestions, see this first. You can do this as of 4.9p1 without resorting to crazy tricks. http://blogs.techrepublic.com.com/opensource/?p=229
