Hi, 

Indeed, it seems that you are right when you say that udev is not reponsible 
for this. I found out that a process from devicekit-disks and one related with 
hal is polling my cd-rom drive so often:  


root      1632  0.0  0.2   3336  1192 ?        S    23:51   0:00 hald-runner
root      1698  0.0  0.2   3400  1140 ?        S    23:51   0:00 
hald-addon-input: Listening on /dev/input/event0 /dev/input/event2 
/dev/input/event1
106       1700  0.0  0.2   3256  1112 ?        S    23:51   0:00 
hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root      1701  0.0  0.2   3404  1128 ?        S    23:51   0:00 
hald-addon-storage: polling /dev/hdc (every 2 sec)


root      1991  0.0  0.5   5036  2844 ?        S    Jan21   0:00 
/usr/lib/devicekit-disks/devkit-disks-daemon
root      1992  0.0  0.1   4796   888 ?        S    Jan21   0:00 
devkit-disks-daemon: polling /dev/hdc       



If I kill the devkit-disks-daemon process, then the problem dissapears. 


ii  hal                                  0.5.14-1                   Hardware 
Abstraction Layer
ii  hal-info                             20091130-1                 Hardware 
Abstraction Layer - fdi files
ii  libhal-storage1                      0.5.14-1                   Hardware 
Abstraction Layer - shared library for storage
ii  libhal1                              0.5.14-1                   Hardware 
Abstraction Layer - shared library


ii  devicekit-disks                      009-2                      abstraction 
for enumerating block devices
ii  devicekit-power                      013-1                      abstraction 
for power management



Cheers!.
 


On Tue, 19 Jan 2010 12:46:51 +0100
[email protected] (Marco d'Itri) wrote:

> On Dec 27, Marco d'Itri <[email protected]> wrote:
> 
> > Great. Try renaming it and then you will have verified that udev is not
> > responsible for this. (Obvious suspects: HAL, gnome-volume-manager.)
> > If you need help, /msg Md on freenode.
> Are there any news?
> 
> -- 
> ciao,
> Marco



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to