as long as your cronjob cycle is longer than your typical chef client convergence you can set it to zero and it should almost never get triggered -- it might go off when it loses a race with you on the command line, but the major cause is going to be that you've got a chef-client run stuck on an nfs mountpoint somewhere in which case spamming the logs with exceptions and having it screaming for help is probably what you want...