Quote:
Originally Posted by orbea
<<snip>> ...
This function someone else (I don't recall who) posted here at LQ a while ago should report any stale pids from programs that have been upgraded and not restarted.
<<snip>> ...
|
Thanks AGAIN orbea.
I was able to put your bash function to work this morning after today's SAMBA update on Slackware64 14.2 + MultiLib.
-- kjh
After the updates and rerunning Alien Bob's massconvert.sh script and `upgradepkg samba-compat32-4.4.16-x86_64-3_slack14.2compat32` :
Code:
# find-stale-pids # I added a bash-wrapper in my $PATH around your stale_pids function :)
2608
# find-stale-pids -v # what open file is stale ?
2608 /usr/lib64/libtdb.so.1.3.8 (deleted)
2765 /usr/lib64/libtdb.so.1.3.8 (deleted)
2769 /usr/lib64/libtdb.so.1.3.8 (deleted)
3244 /usr/lib64/libtdb.so.1.3.8 (deleted)
4616 /usr/lib64/libtdb.so.1.3.8 (deleted)
I do not run SAMBA on my Laptop ... what process has libtdb open ?
Code:
# ps -ef |grep -E '(^UID|[2]608)'
UID PID PPID C STIME TTY TIME CMD
konrad 2608 1 0 Mar12 ? 00:00:05 kdeinit4: kded4 [kdeinit]
So I need to exit KDE ... NICE !!!