Re: CmdSchedule table fscked

[Jason Pincin <chardros@linuxkb.org>]

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

I converted them to varchars, they now support anything.

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

I put a few records in each which show how they relate to one
another, and how scheduling may/will work.

> 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).

I added a timeout field to ExternalCmds that yoiu can use.  0 should
mean no time out, which should be used VERY spaingly.

> 4)  What is the ValidObjectTypes field used for?

Thats what objecttype's that command can be run against.  I gave two
examples in the sample data.  This will be NULL if the external
command doesn't deal with objects.

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

Dir where the executable is.  It's the full path name, including the
executable.  My samples don't have the path, just the executables
name, but it'll be a standard unix path.

> 6)  What is TargetObjects used for?

For scripts that deal with objects, this will pass in the object ID's
that the scripts will run against.  These should be simply passed to
the executable as parameters.  The script will grab them and do it's
magic.  This will once again be NULL if the script doesn't deal with
objects.


Does that take care of everything you need?

-- 
Jason Pincin
Linux Knowledge Base Project Leader (http://www.linuxkb.org/)
http://vodka.linuxkb.org/~chardros/