sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen
- From: Eric Sandall <eric AT sandall.us>
- To: Seth Alan Woolley <seth AT positivism.org>
- Cc: sm-discuss <sm-discuss AT lists.ibiblio.org>
- Subject: Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen
- Date: Thu, 18 Aug 2005 10:03:02 -0700 (PDT)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 18 Aug 2005, Seth Alan Woolley wrote:
<snip>
We can have the general defaults be:
1. Never Restart
2. Don't Restart unless spell hints restart is safe <-- default
3. Restart unless spell hints restart is unsafe
4. Always Restart
Hint policy: if it breaks both on restarting and not restarting, default
to not restart.
init scripts could have:
UPGRADE_SAFE="yes" to hint that restarting is ok (won't restart under option
1)
UPGRADE_SAFE="no" to hint restarting is not ok (will restart under option 4)
UPGRADE_SAFE undefined hints that restarting is going to be assumed to be not
ok under option 2 (default), ok under option 3.
Of course per-spell/during-configure selection would override this behavior.
I assume that takes care of most anybody's concerns (besides it being
"more work"/"too much choice").
I'm assuming there'll be another Sorcery menu for choosing which
default the user wants?
How can we define 'safe'? Shall we assume that the user has been
keeping up-to-date with all the prior updates so we only need to worry
about when ++VERSION changes config file formats and not worry if user
is on VERSION-{a couple of revisions or a major release}?
- -sandalle
- --
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDBL9JHXt9dKjv3WERAtZcAJwPAfS2Egaj++I+hh95cwOxO2pNgwCfSEp3
sarXDDAKUis0XuxYKVHAD/U=
=2qeS
-----END PGP SIGNATURE-----
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen
, (continued)
- Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen, Eric Sandall, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Paul Mahon, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
David Brown, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Eric Sandall, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Arwed von Merkatz, 08/18/2005
- Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen, David Brown, 08/19/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Arwed von Merkatz, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Eric Sandall, 08/18/2005
- Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen, Seth Alan Woolley, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
David Brown, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Seth Alan Woolley, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Seth Alan Woolley, 08/18/2005
- Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen, David Brown, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Eric Sandall, 08/18/2005
- Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen, Seth Alan Woolley, 08/18/2005
-
Re: [SM-Discuss] Starting and Stopping critical services when upgrades happen,
Seth Alan Woolley, 08/18/2005
Archive powered by MHonArc 2.6.24.