On Sat, 2017-09-09 at 09:34 -0400, Sam Varshavchik wrote: > Patrick O'Callaghan writes: > > > NB: "replace" means "unlink the old one and create the new one with the > > same name", e.g. using "mv". Overwriting the old file with new data is > > different and in the case of executables or libraries will almost > > certainly cause problems. > > Which is why rpm does not install each file from each package simply be > creating this file and writing it out. rpm always creates the file with a > temporary name, and renames it once it finished writing and closing it. > > In short, there is no valid, technical, fundamental reason why a dnf upgrade > should leave the system in an unstable state, or somehow interfere with any > running daemon; and why a running daemon has to intentionally go out of its > way to frak things up if it was upgraded while it was running. In case it wasn't clear, I'm agreeing with you. However I still would like to know how to restart those services which don't come with a unit file, other than rebooting of course. The problem is that each case is different and many are not reliably documented. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
