[Infrastructures] Best/good/non-sucky way to restart daemons when libs are updated?
Mark Ferlatte
ferlatte@cryptio.net
Tue, 8 Mar 2005 09:55:01 -0800
--rQ2U398070+RC21q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
My infrastructure has been clicking on reasonably well for the last two years
(althought I'm very interested in the ISFS work that's being proposed here),
and I've finally gotten around to dealing with some of the more annoying
misfeatures.
One of the larger issues that I'm facing is that of daemon restarting: I
currently monitor daemons using monit, and restart them if they get updated on
the filesystem. This doesn't catch the case where a library (say, libssl) is
patched, and all of the daemons that use that lib need to be restarted.
I'm currently hacking around this by having all of the daemons that I can
restart with no ill effect just restart themselves once/day, but that's not a
good solution.
Anyone else already solved this? Or is this considered "solved" by scripting
package installs on the client hosts? (Not viable for me, but probably works
great for most folks).
M
--rQ2U398070+RC21q
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFCLeb1OtZWu2tc1lARAmhjAJ95ORbz3bdfwLp4SBgK3waYds4uigCfajFi
Jwl3w6joZO21tOL/I84tS54=
=l67O
-----END PGP SIGNATURE-----
--rQ2U398070+RC21q--