Effects of RedHat up2date (generic)

[der.hans]

Am 07. Nov, 2002 schw=E4tzte George Toft so:

> I have a RH box and run up2date via cron.  Recently it told me:
> =09glibc-2.2.4-31.i386.rpm:     Retrieved.
> =09glibc-common-2.2.4-31.i386.  Retrieved.
> =09Preparing...
> =09Installing /var/spool/up2date/glibc-common-2.2.4-31.i386.rpm...
>
> =09Installing /var/spool/up2date/glibc-2.2.4-31.i386.rpm...
>
> The question is: after updating libraries, do I have to reboot to reload
> them?  It seems to me, if I have some binary in memory that uses some
> library, which is also in memory, that I would have to restart every
> binary running, or simply reboot, for the newer version on disk to take
> effect.

While I agree it seems that things should break, they seem to work fine.
Daemons that have been updated should be restarted. Dependent daemons shoul=
d
be restarted when libraries are replaced.

X finally died on me last year several months after changing out the
underlying system a couple of times ( went to 4.0.x then to 4.1.x from 3.3.=
x
), but I've otherwise been fine waiting for kernel upgrades or new hardware
for reboots.

debian usually restarts daemons during upgrades. Not sure about other dists=
=2E

ciao,

der.hans
--=20
#  https://www.LuftHans.com/    http://www.TOLISGroup.com/
#  Keine Ahnung, was ich dir sagen soll,
#  keine Ahnung und keinen (.)plan. -- die Toten Hosen