On Fri, Jan 13, 2017 at 3:50 PM, Michael Morak <michael.mo...@gmail.com> wrote: > On 13 January 2017 at 23:04, Jorge Almeida <jjalme...@gmail.com> wrote:
> > Almost, but not quite. The problem is that the POSIX standard requires that > any file *must* continue to exist until all file handles pointing to it are > closed. Thus, using your example, when file foo.so gets replaced, the new > foo.so is written to the disk somewhere, but, since foobard holds an open > file handle, the old file is not deleted from the disk yet. At that point, > the content of *both* files (and relevant inodes, etc.) exists on the > *disk*, and, in addition, there is a pending delete operation for the old > file (that is, a "write" operation to /). This prevents / from being mounted > ro, since the pending write must be executed first (hence the message "/ is > busy"). > OK, I think I understand it. > operation and output a list for you. The needrestart script can also try to > automatically restart them for you. I wouldn't want that. Thanks Jorge
