[Novalug] Stand me in the corner.. I've been bad

Garrett Nievin gnievin at comcast.net
Fri Apr 6 18:39:45 EDT 2007


lsof | grep bad_software_lives_here

lsof looks at information on processes and reports on what files they 
have open; fuser looks at files and sees what processes have them open.

Cheers,
Garrett

On Fri, 6 Apr 2007, Palmer wrote:

> I've tried several things but to no avail..
> lsof bad_software_lives_here
>  produces no output at all
> fuser bad_software_lives_here
>  reports that noone is using the directory
>  (that is, when its not responding with a "segmentation fault" error)
> using the fedora rescue disk then attempting to remove the directory
>  responds with the "Device or Resource Busy" message
> As root, chowning bad_software_lives_here to root:root then
>  chmod 777 bad_software_lives_here
>  works but does produces the same error message when I attempt to rmdir
>
> I appreciate all the input several of you have offered, but I'm still stuck.
> Further ideas will be appreciated.
>
>> Someone already mentioned fuser, which can show open file handles. Also
>> try
>> using lsof to see what  has what files opened.
>>
>> Rebooting / init 1  or anything to stop all processes will close the file
>> handle and let you remove the directory for sure. But if you are curious
>> to
>> see what it is that has the directory open, use lsof or fuser.
>>
>> -Nick
>>
>> On 4/5/07, Cliff Palmer <cliff at palmercs.com> wrote:
>>>
>>> I installed some trial software, used it, finished with it, and then
>>> used their supplied uninstaller.  The uninstaller _almost_ worked...
>>>
>>> The software installs in a directory I was instructed to create
>>> immediately off root (i.e. mkdir /bad_software_lives_here) then did the
>>> chgowner/chgmod thing.  When the uninstaller was finished this directory
>>> was empty (ls -alrt as root shows nothing), but the directory was not
>>> removed.
>>>
>>> Attempts to rmdir /bad_software_lives_here produce the cryptic "Device
>>> or resource busy" response.
>>>
>>> I have verified via ps -eF shows no process with that directory named.
>>> I also did a ps - EF before the install and saved the results, then
>>> compared it with the same thing after the install to see what processes
>>> this evil software starts.  None of the identified processes are still
>>> there (or so says both ps and top).
>>>
>>> Can someone show me what to write on the board 50 times that will remove
>>> this directory...
>>>
>>> Thanks
>>> Cliff
>>> *Dunce Cap already mounted*
>>>
>>>
>>> _______________________________________________
>>> Novalug mailing list
>>> Novalug at calypso.tux.org
>>> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>>>
>>
>
>
> _______________________________________________
> Novalug mailing list
> Novalug at calypso.tux.org
> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>


More information about the Novalug mailing list