Arch Linux User Repository

I think I'll leave it as it is now, at least for a while. The feedback I got from one of the devs [1] is that it should be ok to use it like it is now, and hey, it works reliably :p Another package (upower) also handles coming out of suspend/hibernate it with a script, if there was a better way to do things then I guess it would have been used. I'm also planning to add a mkinitcpio hook so the APM can be set very early on, I suppose that will make the service file a bit redundant, I'll still ship the file but not enable the service by default, the user should choose which method to use. As for the discussion, it's probably better to keep it here in the open. [1] http://mailman.archlinux.org/pipermail/arch-general/2012-October/031384.html

Hey, sorry for all the comments, it seems to work once, and then stops... If you prefer that I contact you some other way, like email, let me know.

Hey, sorry for all the comments, it seems to work once, and then stops... If you prefer that I contact you some other way, like email, let me know.

Okay, now it is not working...

In hddapm.service, add "Also=hddapm-reapply.service" (assuming that is what you call the secondary service), and done!

Nevermind about the requires part, I am not sure exactly how to pull another service file with a given service file. I am perusing documentation, though the hddapm-reapply.service works.

All you have to do is make another service file that is required by hddapm.service. cat hddapm-reapply.service [Unit] Description=Sets the Advanced Power Management level for the chosen Hard Disk After=suspend.target [Service] Type=simple ExecStart=/usr/bin/hddapm post RemainAfterExit=yes [Install] WantedBy=suspend.target

That is a good point about the _after_ part of it. I remember reading somewhere that some drives have issues when you set it to 255. In fact, mine just drops it to 254 when I try 255. Maybe 254 would be a more sane default?

Added an option in the configuration file to select the device. Running the script after suspend/hibernate was already taken care of, there is a symlink in /usr/lib/systemd/system-sleep to make it run after suspend/hibernate. I have been looking into how to use only unit files and not rely on /usr/lib/systemd/system-sleep, but I haven't found any examples or information about it, any pointers will be welcome. Also sleep.target.wants doesn't exist on my system, only sleep.target, however my doubt would be how to properly hook it to run _after_ coming out of suspend/hibernate.

I think this is a good idea, but you should make a variable for the desired devce, instead of simply assuming it is going to be /dev/sda. Also, I think that it should be added to the sleep.target.wants, so that it will reapply the settings after it wakes. Good start though.