Re: Perl: CmdSchedule

[Aaron Turner <aturner@linuxkb.org>]

On Tue, 16 Nov 1999, Jason Pincin wrote:

> > 1)  Who do to these scripts run as?  Does it need to vary (ie, does my
> > script need to be suid root?)
> 
> No... we should create a "linuxkb" user on the system... and all scripts
> should run as that user... and I will set up it's enviroment, etc. to
> authenticate properly with MySQL.

Okey doke.
 
> > 2)  Howabout a "email" (text) and "notify" (enum('y','n')) fields?  That
> > way people can get an email of output or sucess/failure if they choose.  I
> > know you suggest we do this later, but I'd rather do this as part of v1.0
> 
> Hm.  I was thinking of something more general... such as build into the
> script eventually or now... to just shoot off a mail when it marks
> something as failed... or maybe we don't care if certain things failed is
> perhaps what your saying?  That is a possibility... and I could add an
> enum field for that... and just defualt it to always notify on failure...
> but have the functions make it possible to turn it off... but not sure
> what the email (text) would do...
> 
> I envision the scheduling system used a LOT eventually... and I'm having a
> hard time envisioning anyone coding into there php pages an email to
> kickoff everytime somone performs a certain action...
> 
> But I could be totally wrong and smoking something bad :).  Do you think a
> generic failure notification that can be turned on/off is good enough in
> which case I'll add a notify enum field?  Or do we want more control than
> that?

I was thinking simplistic, but you tell me.  I just build the tools to
spec, you're the poor slob who actually has to use them. :-)  My guess is
the more power/feature the better, and it really doens't make my code
anymore difficult.