On Tue, Mar 08, 2005 at 10:27:45AM -0800, David M. Fetter wrote:
> Yeah, we actually use cfengine for all of that. Therefore, we have no
> need at all for a package to do any restarting of it's own. One thing
> one of my co-workers mentioned is that it would at least be nice if
> there was a --norestart or something along those lines.
What about simply shutting down the service with cfengine before
deploying the upgrade ? The package will only _re_start the
service if it is already running.
> the problem is that most of the packages seem to copy aside the working
> configs to $config.rpmsave and overwrite it with the default one. If
> instead, the rpms copied the new default configs to $config.rpmnew as a
> standard then at least when it restarted things most likely will not
> break.
Here we again touch philosophical matters. "Most likely" has some
very individual meanings :) I still say: don't trust on this, there
will be exceptions where you cannot rely on "most likely" but where
you must do it right.
Greetings,
--
Michael van Elst
Internet: [EMAIL PROTECTED]
"A potential Snark may lurk in every tree."
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
