On Tue, Sep 29, 2009 at 8:44 PM, Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx> wrote: > > > On Tue, 29 Sep 2009, Bill Nottingham wrote: > >> Seth Vidal (skvidal@xxxxxxxxxxxxxxxxx) said: >>> >>> at the risk of getting myself in trouble - you don't have to do it >>> at the rpm layer... You could do it in yum or in a yum plugin and >>> then not have to worry about propagating it up the stack. >> >> The alternative is to have apps set inotify watches on their own >> binaries, I suppose. (There was something in Fedora that used to >> do this.) > > wow, that would be, umm, special. > > How well does inotify cope with THOUSANDS of watches? 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. -- Fedora-desktop-list mailing list Fedora-desktop-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-desktop-list
