Michael Morak wrote:
> Hi,
>
> I have a similar setup. The problem is that some of your services may
> still have open handles on files that no longer exist after updating
> (i.e. the service, when originally started, opened an .so library file
> that it needs to run, but the file then gets deleted or replaced
> during the emerge -u). Simply restart all services (and other running
> programs) that have locks on files that were updated.
>
> The reason those files do not show up in your lsof command is that
> they may not be open for writing but only for reading. A read lock on
> a file may still give you the "/ is busy" message, since the
> open-for-read file cannot be (fully) deleted while a running
> application still has a lock on it. You have to get the process to
> release the read lock on the file (which, for libraries, is usually
> done by a restart).
>
> Hope this helps.
>
> Cheers,
> Michael
>
When I do a upgrade and need to know what processes or services need to
be restarted, I use this command that someone posted about on here a
long time ago.
root@fireball / # equery b checkrestart
* Searching for checkrestart ...
app-admin/checkrestart-0.47-r3 (/usr/sbin/checkrestart)
root@fireball / # eix checkrestart
[I] app-admin/checkrestart
Available versions: (~)0.47-r3{tbz2} ~0.47-r4
{PYTHON_TARGETS="python2_7"}
Installed versions: 0.47-r3{tbz2}(01:37:05 AM
08/08/2016)(PYTHON_TARGETS="python2_7")
Homepage: http://arcdraco.net/checkrestart
Description: the sysadmin's rolling upgrade tool
root@fireball / #
Maybe that will point out something as well.
Dale
:-) :-)
