Leo Geoffrion - 2006-05-01 13:23:58
When trying to use it I found two minor problems.
1. On many systems the command crontab -u can only be invoked by privileged users. The Readme should warn about this. It's easy to edit these out if you're running this from a nonprivileged account.
2. In the writeCrontab function, the Case statement references CRON_EMPTYLINE when correct name is CRON_EMPTY.
This causes bogus error messages from the default case behavior. Again, it's a simple fix...
