CmdSchedule table fscked

[Aaron Turner <aturner@linuxkb.org>]

Mostly to Jason...

I need:

1)  All the date/time fields to support the cron format we talked about.
Currently they don't.  This means * or [0-23-/,]

2)  Sample data in the tables (including ExternalCmds) for me to query
against.

3)  A timeout field added to table of your choice.  I looked up the
information about how to enforce a "life time" to each command using
fork().  Looks to be quite doable, as long as your scripts accept the
different POSIX SIG's (which I assume Python does, I know Perl/bash do).

4)  What is the ValidObjectTypes field used for?

5)  Is CommandPath the working directory or the directory where the
executable is?

6)  What is TargetObjects used for?

--
Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
Linux Knowledge Base Organization  http://www.linuxkb.org/
Because world domination requires quality open documentation.
aka: aturner@vicinity.com, aturner@pobox.com, ion_beam_head@ashtech.net
The difference between `Unstable' and `Usable' is only two characters: NT