[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strategy for "one-off" tasks
From: |
David Douthitt |
Subject: |
Re: Strategy for "one-off" tasks |
Date: |
Mon, 14 Jul 2003 10:43:24 -0500 |
On Monday, July 14, 2003, at 09:43 AM, Nielsen, Steve wrote:
This is something that I have been wanting to tackle for a while as
well.
Just have not had the time to get around to it. The controlled roll-out
should also include some way to track if a task was completed on a
given
machine. I was planning on implementing something using mysql and a
module
in cfengine. What ideas have you had about this?
My current thinking is to do this with one or two hidden files - an
inversion of the one-off process listed earlier:
classes:
DoUpdate = ( FileExists(/var/cfengine/.update) )
AlwaysUpdate = ( FileExists(/var/cfengine/.update-always) )
shellcommands:
DoUpdate::
"apt-get -q -y update" define=updatedone
AlwaysUpdate::
"apt-get -q -y update"
updatedone::
"rm -f /var/cfengine/.update"
- Re: Strategy for "one-off" tasks, (continued)
RE: Strategy for "one-off" tasks, Ferguson, Steve, 2003/07/11
Re: Strategy for "one-off" tasks, David Masterson, 2003/07/11
RE: Strategy for "one-off" tasks, Ferguson, Steve, 2003/07/11
RE: Strategy for "one-off" tasks, Ferguson, Steve, 2003/07/14
RE: Strategy for "one-off" tasks, Nielsen, Steve, 2003/07/14
- Re: Strategy for "one-off" tasks,
David Douthitt <=
RE: Strategy for "one-off" tasks, Wheeler, John, 2003/07/15