Cron

Getting cron services available to users is a work in progress. Presently, cron is being architected with two sides:

Permission details

The tricky part of cron on UGCS is to make some way so the daemon can get tokens for the user. Currently, the procedure looks like this:

• The daemon runs with kerberos tokens for ugcs_cron on the server. It uses a remctl to "call" the appropriate line of the user's crontab
• The remctl, as one of its arguments, is given the user's /cron keytab. The remctl script decodes this, puts it in a temp file, and calls kinit
• The remctl then calls "ksu user -e cron_command"
• The remctl script also watches to make sure the command doesn't go on for too long
• If necessarily, the remctl script