Am 02.11.2013 21:02, schrieb Richard Hughes:
On 2 November 2013 17:47, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
> I'm not really excited about a lot of required rebooting, though -- I think
> that might be worse than the disease. We should have most of the information
> needed to determine if a reboot is really necessary, shouldn't we? I hope we
> can move to that in the future for a nicer user experience.
There's no way to tell if an application can be updated on-line due to
runtime loadable content and plugins. It's also impossible to do in a
race-free way on a multiuser system.
why?
"lsof | grep DEL | grep /usr" shows any opened but deleted file
which is the case after updfates while applications are running
hence that is what i use on a infrastructure with around 20
Fedora servers to decide which services needs restarts or it
is worth to reboot which is hadrly the case except after kernel-updates
instead going the easy windows-way and say "ok, you have to reboot"
it would be more worth to optimize the handling *after* updates
without reboot and let the user decie wichi services are needed
to restart
yes i am strictly against "restart services after updates" why i
build any server related package by myself since years because
i know the impact of a update and most time a blind restart
at a random moment has more bad impact
_______________________________________
[root@buildserver:~]$ cat /buildserver/distribute-needs-restart.sh
#!/usr/bin/bash
distribute-command.sh "/usr/sbin/lsof | grep DEL | grep /usr"
[root@buildserver:~]$ cat /buildserver/distribute-command.sh
#!/usr/bin/bash
source /Volumes/dune/buildserver/server-list.txt
function rh_run_command
{
echo -e "\e[32m$1\e[0m"
/usr/bin/ssh root@$1 "$2"
echo ""
echo -e
"\e[31m--------------------------------------------------------------------------\e[0m"
echo ""
}
if [ "$2" == "" ]
then
echo "" > /dev/null
else
echo "Put your params in quotes"
exit
fi
for item in ${RH_TARGET_SERVERS[*]}
do
rh_run_command $item "$1"
done