On Fri, Jul 27, 2001 at 10:58:55AM -0400, Louis A. Mamakos wrote:
> > Matthew Emmerton([EMAIL PROTECTED])@2001.07.26 16:50:52 +0000:
> > > On Thu, 26 Jul 2001, Matthew Jacob wrote:
> > >
> > > > It'd be nice if one could pass a time specification to at in the form of "next
> > > > reboot".
> > > >
> > > > -matt
> > > >
> > >
> > > Why not just write a script for the command and stick it in
> > > /usr/local/etc/rc.d?
> >
> > because a uid != 0 won't write a startup file there, won't he? ;-)
>
> Of course, he could use the crontab(1) command, and install an
> entry with a time of '@reboot'.
>
> RTFM: man 1 crontab
> man 5 crontab
>
> Sure, this starts something on *every* reboot, but that's the same
> as if you installed someting in /usr/local/etc/rc.d
[CC list trimmed viciously]
So cron allows a @reboot specification, but at(1) (which is invoked
by cron, btw - but that's an implementation detail) does not?
This seems like lack of parallelism..
IMHO, there's nothing wrong in adding that functionality to at(1).
If people don't like it, they won't use it :)
G'luck,
Peter
--
This sentence was in the past tense.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
