cronload should error when run without arguments

[adehnert]

At the moment, if you run cronload with no arguments, it'll give you an error message from cat, and wipe your crontab:

[asa@cats-whiskers]:~/Scripts/django/db2.0/asadb$ cronload
/bin/cat: : No such file or directory
New crontab for asa:

[asa@cats-whiskers]:~/Scripts/django/db2.0/asadb$ 

Instead, it should give you a nice error message and not touch your crontab, or something.

[btidor]

Works for me...

btidor@mary-kay-commandos:~/cron_scripts$ cronload
Usage "/mit/scripts/arch/i386_rhel3/bin/cronload [-l lockername] [-h] crontab"

[andersk]

The cronload you ran from the locker is actually a wrapper script around the cronload you get while logged into scripts. This bug is about the latter, and it looks like it still exists.

[btidor]

Also occurs if the named cronfile does not exist. Fixed; see patch.

[andersk]

The message should be printed to stderr, and the exit status in these cases should be nonzero.

[ezyang]

Committed in r2313, thanks for the patch! (For future reference, it's good to have the svn diff be from the root directory of the repo, so that the filename is identified; there are three files named cronload in our repo!)