Re: Time & CmdSchedule

[Jason Pincin <chardros@linuxkb.org>]

Because the point is, for the develoeprs to be able to easily schedule anything they want on
the fly.  Or for the underlying objects to be able to add things and remove them from the
schedule.

We are developing a Perl script that will run via Cron every minute, and it will query the
table CmdSchedule, and run whatever that table tells it to..  That's how it will work... or
rather - how we're suggesting it works.  It's really not that complex.

Jason


On Sat, Dec 04, 1999 at 01:58:38AM -0500, sporty wrote:
> why not write one single script that is called by cron.  then you can use
> your favourite shell language or script language to do whatever you
> want... 
> 
> or write a small perl script that keeps running and does whatever you
> want?  sounds like you are making mountains out of mole hills...
> 
> On Fri, 3 Dec 1999, Jason Pincin 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?
> > 
> > That's no good.  Cron doesn't support the features we need.  And it would take more system time to
> > add a task to a user's physical crontab file than it would to do a single table DB insert I believe.
> > But even if it didn't... we need the functionality we're describing...
> > 
> > -- 
> > Jason
> > http://vodka.linuxkb.org/~chardros
> > 
> > 

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