Comment 78 for bug 59695

As I promised, here are the results of the test. I replaced hdparm with a script and logged what happened.
So, here we have the proof that actually the scripts ARE altering the default settings.
<<start>>
Fri Oct 26 01:28:00 EEST 2007 hdparm invoked with parameters -S 4 /dev/sda
...[pstree]
     |-apmd---apmd_proxy---run-parts---laptop-mode---laptop_mode---hdparm---pstree
...
-----------------------------------
Fri Oct 26 01:28:17 EEST 2007 hdparm invoked with parameters -S 244 /dev/sda
init-+-apmd---apmd_proxy---run-parts---laptop-mode---laptop_mode---hdparm---pstree
     |-klogd
     `-rc---S20sendsigs---sleep
-----------------------------------
Fri Oct 26 01:29:33 EEST 2007 hdparm invoked with parameters -S0 /dev/sda
...[pstree]
     |-rc---S20hdparm---S20hdparm---hdparm---pstree
...
-----------------------------------
Fri Oct 26 01:29:37 EEST 2007 hdparm invoked with parameters -S 4 /dev/sda
init-+-NetworkManager
     |-NetworkManagerD
     |-apmd---apmd_proxy---run-parts---laptop-mode---laptop_mode---hdparm---pstree
     |-console-kit-dae---61*[{console-kit-dae}]
     |-cron
     |-dbus-daemon
     |-dd
.....[more pstree cut]
<<< end >>>

All I did was to reenable the acpid and apmd services and reboot... I also mention that on this system on_ac_power returns 255 and the system does not interpret correctly this sittuation and activates a laptop specific on-battery profile(this is another bug) . This is actually a desktop system.