From owner-freebsd-hackers Thu Jul 26 10:32:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 71F0137B405 for ; Thu, 26 Jul 2001 10:32:06 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 58606 invoked by uid 1000); 26 Jul 2001 17:31:13 -0000 Date: Thu, 26 Jul 2001 20:31:13 +0300 From: Peter Pentchev To: Matthew Jacob Cc: hackers@freebsd.org Subject: Re: perhaps one of phk's "intern" projects? Message-ID: <20010726203113.D53502@ringworld.oblivion.bg> Mail-Followup-To: Matthew Jacob , hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Thu, Jul 26, 2001 at 10:20:51AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 26, 2001 at 10:20:51AM -0700, Matthew Jacob wrote: > > It'd be nice if one could pass a time specification to at in the form of "next > reboot". This could be implemented as a startup script, no? On second thoughts, not quite trivial. It wouldn't be hard to write a separate utility to schedule jobs to be serviced at the next reboot; integrating this functionality into at(1) would be nice, too, though maybe just a little bit harder - it would require the time to parse the at(1) sources ;) Then it would be as simple as making the command-line scheduling utility write the job into the at-next-boot utility spool dir instead of the regular at(1) spool dir; or maybe the at-next-boot utility could just look through the regular at(1) spool dir for some specially-marked files that at(1) would ignore.. I would be willing to do this, if no one else volunteers. G'luck, Peter -- This would easier understand fewer had omitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message