re mandrake 10

I get device busy when I try to unmount the cdrom
from the dektop icon and eject fails also'
A google search shows some others having the same
problem but no solution.
Running fuser as root shows a pid using "/mnt/cdrom2"
the pid number does not show up in top.
How can I identify a program number from it's PID.
--
faeychild

* <deimos@yaahoo.com> wrote:
> Running fuser as root shows a pid using "/mnt/cdrom2"
> the pid number does not show up in top.
> How can I identify a program number from it's PID.

ps -ef | grep THEPIDHERE

Davide

--
| (null cookie; hope that's ok)
|
|
|

* wrote:

> re mandrake 10
>
> I get device busy when I try to unmount the cdrom
> from the dektop icon and eject fails also'
> A google search shows some others having the same
> problem but no solution.
> Running fuser as root shows a pid using "/mnt/cdrom2"
> the pid number does not show up in top.
> How can I identify a program number from it's PID.

UPDATE
The program using the cdrom is called "FAM"
killing fam releases the cdrom.
How do these things ever get past testing?, it
seems another,maybe not useless but, annoying
bell and whistle.
It can be stopped by removeng it's command from "/etc/inetd.conf"
pity I can't find this file in mandrake, not on that path anyway.


--
faeychild

faeychild wrote:

> UPDATE
> The program using the cdrom is called**"FAM"

the FAM package contains a "File Alteration Monitor"
that is used to notify apps of changes to the filesystem
..
--
<< http://michaeljtobler.homelinux.com/ >>
B Integer out of range, 0:1

faeychild wrote:

> * wrote:
>
>> re mandrake 10
>>
>> I get device busy when I try to unmount the cdrom
>> from the dektop icon and eject fails also'
>> A google search shows some others having the same
>> problem but no solution.
>> Running fuser as root shows a pid using "/mnt/cdrom2"
>> the pid number does not show up in top.
>> How can I identify a program number from it's PID.
>
> UPDATE
> The program using the cdrom is called "FAM"
> killing fam releases the cdrom.
> How do these things ever get past testing?, it
> seems another,maybe not useless but, annoying
> bell and whistle.
> It can be stopped by removeng it's command from "/etc/inetd.conf"
> pity I can't find this file in mandrake, not on that path anyway.
>
>
Maybe you can find a *fam file in the /etc/xinetd.d/ directory.
Add (or change) the option

service fam
{
...
disable = yes
}

and restart the xinetd program.

(Xinetd is the successor of inetd)