RE: [rpm-list] Starting and stopping daemons?

["Jason Pyeron" <jpyeron@xxxxxxxx>]

well it depends...

 

you do not want the upgrade to interrupt a user experience unexpexedly, look at how sshd/glibc does that.

 

also on linux systems you can replace files that are in use without changing the contents from the perspective of those using the files.

 

I would say that you should not restart the daemon, unless it is expected and without harm (xinetd,sshd).

 

-Jason

 

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Principal Consultant              10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.

 

---

From: rpm-list-bounces@xxxxxxxxxxxxx [mailto:rpm-list-bounces@xxxxxxxxxxxxx] On Behalf Of Dan Stromberg
Sent: Tuesday, March 13, 2012 18:02
To: General discussion about the RPM package manager
Subject: [rpm-list] Starting and stopping daemons?

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