Beware of crontab - l

You have cron jobs running in Prod server and everyone is happy about it. Also you don't have the backups of cron entries. Now, by mistake, one of the junior dba executed the command crontab - l instead of running crontab -l. The cron did hang at this moment of time. To come out of this, he entered ctrl-d and exited out of the session as well as from putty. The next shift started and the other dba thought of checking the crontab entries and thus executed the command crontab -l...Eureka. He could not see any cron entires. Unix team forwarded the log file /var/log/cron and the term "REPLACE" was logged in when the dba executed ctrl-d. So be careful next time.