Re: Time & CmdSchedule

[Jason Pincin <chardros@linuxkb.org>]

> that I'm not sure we're willing to give up.  Also maintaining the crontab
> file will be a pain in the butt (it's going to get really big)

Another good point.  When the system gets rolling, I could see in the range of 100+ tasks scheduled
at any given time, and it'll be changing rapidly... those are the kinda things plain old ascii files
SUCK at. 100+ may be a VERY low estimate as well... depending on low-level object usage. 

> Oh, Jason, I think it would be really nice to have a comment field in the
> CmdSchedule table.

Can do.

> 
> On Fri, 3 Dec 1999, Daniel E. Markle wrote:
> 
> > On Thu, Dec 02, 1999 at 10:27:10PM -0800, Aaron Turner wrote:
> > > that you created the scheduling system very cron like.  Not being a cron
> > 
> > Instead of recreating the wheel here, why not just have scheduled jobs put
> > cron jobs calling the CmdSchedule script with a function at the right time
> > into nobody, or some other user's crontab?
> > 
> > -- 
> > -------------------
> > Daniel E. Markle
> > syntax@ashtech.net
> > http://www.ashtech.net/syntax
> > -------------------
> > 
> 
> --
> Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
> Linux Knowledge Base Organization  http://linuxkb.org/
> Because world domination requires quality open documentation.
> aka: aturner@vicinity.com, aturner@pobox.com, ion_beam_head@ashtech.net

-- 
Jason
http://vodka.linuxkb.org/~chardros