[Infrastructures] Best/good/non-sucky way to restart daemons when libs are updated?

[DJ Gregor]

You could run "ldd" on each of the daemons and check the update time on 
the libraries listed.


	- djg

On Mar 8, 2005, at 12:55 PM, Mark Ferlatte wrote:

> 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