Réf. : Réf. : [9fans] Auth & cron

["Fco. J. Ballesteros" <nemo@gsyc.escet.urjc.es>]

>>>>> "boyd" == boyd roberts <boyd.roberts@ca-indosuez.com> writes:

    boyd> you miss the point.  you have to physically enter some data.
    boyd> this involves the data, a keyboard and your fingers.  read
    boyd> the auth protocol docs.

Already read them; but let's re-read them.... done :-)

As I thought, you authenticate (using your keyboard and your
fingers;-) ) when you boot your terminal.

But, after you got your terminal running, you can use cpu to run your
`cron' process on a cpu server. If the cron process keeps on hanging
around even after you reboot your terminal, it can maintain your cron
entries.

The cron process is already authenticated and should be able to spam
new processes to run your cron entries. 

What I don't like is 

1: rebooting your cpu server makes your cron die and forget your
   entries. 
   (a workaround would be to check that it is running when you log in,
    and spawn a new cron otherwise; but that's not a fix).

2: one process per-user rather than one per site (although that may be ok).

-- 
    ()    ascii ribbon campaign - against html mail 
    /\                          - against microsoft attachments