[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Strategy for "one-off" tasks

From: Ferguson, Steve
Subject: RE: Strategy for "one-off" tasks
Date: Mon, 14 Jul 2003 09:50:08 -0400

Yes, but cron has no capability to distribute a script to over a hundred
systems.  Scripts to change over time, and in our environment NFS is not
usable between our internal and our DMZ hosts.  So some sort of copying
mechanism (preferably one that supports encryption) is required.

I guess my view is that if I've gone to all the trouble to set up cfengine,
and it comes with all these neat bells and whistles, I'd like to actually
use them.

Because I can come up with a viable strategy, I plan to use it.  cron
doesn't meet my needs, additionally because I might decide I need an audit
before the next cron run was scheduled.  With cfengine I can do an immediate
cfrun.  With cron, no such luck.


> -----Original Message-----
> From: Jamie Wilkinson [mailto:address@hidden
> Sent: Friday, July 11, 2003 10:09 PM
> To: 'address@hidden'
> Subject: Re: Strategy for "one-off" tasks
> This one time, at band camp, Ferguson, Steve wrote:
> >I have a software audit script.  It'll report all packages 
> on the system
> >from a particular vendor.  I only want to run this once, get 
> the output, and
> >send it off to the business types who have to reconcile it 
> with invoices and
> >budgeting.
> >
> >It's done maybe annually, if that often.  I only want it run when I'm
> >sitting there, at the keyboard, actually looking at the 
> output.  So it's
> >essentially a once-only manual task.
> You know, cron didn't disappear when cfengine arrived ;-)  I 
> use cfengine to
> maintaing a few crontabs; you could get the job to mail you 
> and that way
> you'll be sitting at the keyboard to look at the output.
> -- 
> address@hidden                           
> _______________________________________________
> Help-cfengine mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]