The module can't be removed, because it's busy (used)

[Rava]

In some older Port versions one got a small info window telling me what program is blocking a module and probably the reason why it cannot be deactivated.

But when I try to run

Code: Select all

# deactivate /mnt/live/memory/images/05-devel.xzm
05-devel.xzm: The module can't be removed, because it's busy (used).

I get this in console and a GUI window telling me the similar info (differently phrased)

I recall lsof was one of the programs one could use to find the culprit process, but forgot the other.

What about a script that looks for folders with executable files, and then looks if any of these paths are still open by some program?
I tried compiling stuff weeks ago (it failed, here the info http://forum.porteus.org/viewtopic.php? ... 566#p43559 )

What do you folks think of my idea?

[francois]

I have the same problem as you and finally just got used to it.

When I achieve to get out, it is by closing folders implicated, for example after umount of usb stick. Otherwise, nothing would make a change, not even log out of X.

Here is what I found to get rid of background processes:
http://unix.stackexchange.com/questions ... nd-process

[Rava]

Thanks francois, by now I restarted my whole machine and solved the issue by that.


But this is the very last approach to this issue. usually I look up every terminal and virtual terminal, and usually somewhere a mc is open, started in a path that is part of the activated module. But not this time, I tried every single VT or T, to no avail...

I wonder, what did happen to the info window that told us which process is using the module we want to deactivate.
Porteus used to have that window, but at least in current version (3.1) I don't see it anymore.

[francois]

There is nothing in Porteus Settings Center?

[Rava]

There is nothing in Porteus Settings Center?

I looked it through but did not find anything.