[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strategy for "one-off" tasks
|
From: |
Ted Zlatanov |
|
Subject: |
Re: Strategy for "one-off" tasks |
|
Date: |
Tue, 15 Jul 2003 12:23:56 -0400 |
|
User-agent: |
Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (usg-unix-v) |
On Tue, 15 Jul 2003, ssrat@mailbag.com wrote:
> WHile we're discussing it - why not write your code like this
> instead?
>
> classes:
>
> AlwaysUpdate = ( FileExists(/var/cfengine/.update-always) )
>
> shellcommands:
>
> DoUpdate||AlwaysUpdate::
> "apt-get -q -y update && touch /var/cfengine/.updatedone"
It's six one way, half dozen the other... I think it's cleaner to
define a separate class, but your way is just as good in its brevity.
Ted
- Re: Strategy for "one-off" tasks, (continued)
- 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, Wheeler, John, 2003/07/15