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.32976.222013.344094@nautilus.dat.escet.urjc.es> Date: Tue, 18 Jul 2000 17:07:44 +0100 To: 9fans@cse.psu.edu Subject: =?iso-8859-1?Q?R=E9f._:_[9fans]_Auth_&_cron?= In-Reply-To: <41256920.0056816E.00@SNPAR12.> References: <41256920.0056816E.00@SNPAR12.> Topicbox-Message-UUID: e1f0a106-eac8-11e9-9e20-41e7f4b1d025 >>>>> "boyd" == boyd roberts writes: boyd> but how do you auth the user? there is no setuid. you Just like you are doing it now to run processes on the cpu server. But you'll keep your `cron' process running forever. The only bad point I see is that a cpu server reboot will drop your cron entries. boyd> so you gotta enter some data to auth yourself. this data boyd> must _never_ cross the wire. so if you say server x is my boyd> preferred cron server, just how is server x's cron going to boyd> get the auth data to allow the cron to 'run as you'? How are you doing that to run your process on your cpu sever? IMHO it can be done the same way. But, as I said, I may be missing something. -- () ascii ribbon campaign - against html mail /\ - against microsoft attachments