|Date:||Thu, 11 Nov 2004 17:10:33 +0100|
I'm struggling with a design i thought it could implement an update system but the import directive behaviour is driving me crazy.
The idea is to downlad a list of available patches (within cfengine)
compare with the workstation latest applied patch and declare classes conforming new available and not applied updates (module:version)
import and execute pending update cfengine scripts (within cfengine)
The tricky part is the last listed above:
If I write it like this it doesn't work even if I declare de classes as addinstallable (not addinstallables as stated in documentation):
And if I write it like that it doesn't finish the whole initial parse because the update_*.conf files are not found:
If it was the initial deployment I would copy all the update files within update.conf. But now I can't modify it and assure that in the future the installed workstatinons that have been installed and not being booted in will enter correctly in the update cycle.
Thanks in advance.
P.D: Using Debian cfengine2 package ( version 2.1.10-2 )
_______________________________________________ Help-cfengine mailing list Help-cfengine@xxxxxxx http://lists.gnu.org/mailman/listinfo/help-cfengine
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Mark Burgess|
|Next by Date:||Re: import behaviour, Brendan Strejcek|
|Previous by Thread:||Re: cfexecd, FatalError(), leaves cfagent burning 100% cpu, Jamie Wilkinson|
|Next by Thread:||Re: import behaviour, Brendan Strejcek|
|Indexes:||[Date] [Thread] [Top] [All Lists]|