tis 2009-09-29 klockan 20:46 +0200 skrev drago01: > There is a 8k limit for non root users, besides that sounds racy (what > if the binary changed but some lib is still not updated and the soname > got bumped?) so it will restart itself while the upgrade process is > still running an fail. Hmm, true. When rpm is done with a transaction, it provides a list of files it modified. The next step is to send a signal to all processes that has any of those files open and has indicated that it is capable of dealing with such signals, so that the process can take appropriate action. That should catch the binary and all loaded libraries. Should be enough, right? Maybe DBus is the right way to broadcast that list of files? Either send the whole list to all recipients that asks for it or filter it for each process based on its open files. In the case of shared roots, you want to do this on each machine that has this filesystem mounted. Can't it just be a program that takes a list of paths on stdin and broadcasts it? Normally run directly by rpm or yum but in some cases triggered by other means, like manually when the sysadmin released an update to the shared root? /abo -- Fedora-desktop-list mailing list Fedora-desktop-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-desktop-list
