Comment 84 for bug 379780

OK I just found a way to drop the CPU load without stopping udev. The trouble is I cannot confirm that this method will work because I was not able to re-duplicate it before posting, so your mileage might vary. Here is what I did:

# hal-disable-polling --device /dev/sr0

It printed a bunch of messages that got lost because I did a top to check the load and was surprised to find that the CPU load dropped instantaneously!!

The funny thing (to me) is if HAL was dropped from Lucid and if I did a fresh install of Lucid so the /etc scripts should not have had any initialization of HAL, why then should any HAL stuff be running?? I sometimes saw: hal-addon-stor running but never thought of stopping it until now. What is even more strange to me is when I do the following right now:

# ps ax|grep hal

 I see:

1862 ? Ssl 0:00 /usr/sbin/hald
 1863 ? S 0:00 hald-runner
 1899 ? S 0:00 hald-addon-input: Listening on /dev/input/event5 /dev/input/event10 /dev/input/event7 /dev/input/event6 /dev/input/event2 /dev/input/event1 /dev/input/event9 /dev/input/event3 /dev/input/event0
 1902 ? S 0:00 /usr/lib/hal/hald-addon-rfkill-killswitch
 1903 ? S 0:00 /usr/lib/hal/hald-addon-leds
 1913 ? S 0:00 /usr/lib/hal/hald-addon-generic-backlight
 1921 ? S 0:00 hald-addon-storage: no polling on /dev/sr0 because it is explicitly disabled
 1926 ? S 0:00 /usr/lib/hal/hald-addon-cpufreq
 1927 ? S 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
 3650 pts/1 S+ 0:00 grep hal

So what's going on? Has HAL truly been disabled or what? Any serious explanation of what happened to solve the problem for me would be much appreciated. The load kind of instantly dropped and do not come back after restarting my laptop, which is a good thing in my book. :)