Is there any preexisting net.wisdom available on whether rpm's should/shouldn't stop or start the daemons they're changing?
That is, is the admin expected to stop a service before an rpm upgrade, and then start again afterward, is it also acceptable for an rpm to auto-detect that the daemon is up, stop it, do the upgrade, then resume it?
Thanks!
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list
