In what world is it a reasonable Sysadmin action to stop cron entirely, just to avoid an (otherwise-harmless) email alert from one cron job out of 30+ jobs on a host?
I am not sure why this particular insanity is boggling my mind so much today. (Perhaps some of it is due to the Sysadmin in question first trying to use 'svcadm diable cron' -- FOUR TIMES -- before realizing their typo.)