From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fco. J. Ballesteros" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14708.36749.28695.762166@nautilus.dat.escet.urjc.es> Date: Tue, 18 Jul 2000 18:10:37 +0100 To: 9fans@cse.psu.edu Subject: =?iso-8859-1?Q?R=E9f._:_R=E9f._:_[9fans]_Auth_&_cron?= In-Reply-To: <41256920.005A93E2.00@SNPAR12.> References: <41256920.005A93E2.00@SNPAR12.> Topicbox-Message-UUID: e22f4cc6-eac8-11e9-9e20-41e7f4b1d025 >>>>> "boyd" == boyd roberts 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