Yes, that's the basic problem. I don't see how it's possible to use Cfengine's package management facility to handle updating the Solaris Cfengine package, given there's no package update/upgrade command on Solaris, only pkgrm and pkgadd. Thus you'd have to have it remove the current package to install the new one, wiping out the binaries that are actually performing the upgrade in the process. Linux is simpler, given the -U update option to the rpm command. Thus, if Cfengine is deployed to Solaris hosts with a package, as is done with Nova, and subsequent binary updates are done via the standard update.cf, that is going to "break" the Solaris package database.
Justin -----Original Message----- From: nwat...@symcor.com [mailto:nwat...@symcor.com] Sent: Thursday, December 17, 2009 12:16 PM To: Justin Lloyd Cc: help-cfengine; help-cfengine-boun...@cfengine.org Subject: Re: Updating Solaris cfengine binaries If I understand you correctly you have a problem with two masters. CF is updating binaries but so is the Solaris package manager. Only one service should be in charge of keeping CF binaries up to date. Either is fine but be consistent. Sincerely, -- Neil Watson 416-673-3465 This electronic communication and any attachments may contain confidential and proprietary information of DigitalGlobe, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient, or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received. DigitalGlobe reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
