From owner-freebsd-mobile Wed Feb 11 13:49:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28287 for freebsd-mobile-outgoing; Wed, 11 Feb 1998 13:49:10 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from socrates.i-pi.com (socrates.i-pi.com [198.49.217.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28269 for ; Wed, 11 Feb 1998 13:49:04 -0800 (PST) (envelope-from ingham@i-pi.com) Received: (from ingham@localhost) by socrates.i-pi.com (8.8.7/8.8.7) id OAA20527; Wed, 11 Feb 1998 14:47:23 -0700 (MST) (envelope-from ingham) Message-ID: <19980211144722.40814@i-pi.com> Date: Wed, 11 Feb 1998 14:47:22 -0700 From: Kenneth Ingham To: Andrew McNaughton Cc: FreeBSD Mobile Subject: Re: Alternatives to cron (was Re: PCMCIA Card Config) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Andrew McNaughton on Thu, Feb 12, 1998 at 09:30:37AM +1300 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 12, 1998 at 09:30:37AM +1300, Andrew McNaughton wrote: > I have another process in mind > which _must_ go ahead every night, but needn't be at an exact time. cron > doesn't handle this well if the server goes down briefly at the wrong > moment, or in rare cases has too high a load and misses a cron job. What about a self-rescheduling at job? at jobs which should have run while the system was down will run when it comes back up. Kenneth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message