Package Details: systemd-hddapm 1.6-2

Git Clone URL: https://aur.archlinux.org/systemd-hddapm.git (read-only)
Package Base: systemd-hddapm
Description: Hard Disk APM level service for systemd
Upstream URL: https://sourceforge.net/projects/hddapm
Licenses: GPL
Submitter: R00KIE
Maintainer: R00KIE
Last Packager: R00KIE
Votes: 15
Popularity: 0.000014
First Submitted: 2012-09-24 20:29
Last Updated: 2017-07-23 12:01

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

PerfectGentleman commented on 2013-05-22 02:05

is /etc/hddapm.conf not needed anymore?

R00KIE commented on 2013-05-21 11:14

Paths updated to /usr/bin/*

stativ commented on 2013-05-20 15:51

There's a new hdparm being brewed in testing that has the hdparm binary moved from /sbin/hdparm to /usr/bin/hdparm.

Anonymous comment on 2013-01-29 17:15

Simply and great for WD Green series! Thanks!!!

gdamjan commented on 2012-11-07 00:06

This should probably be merged with the hdparm package in [core]

WonderWoofy commented on 2012-10-03 03:48

I didn't even think about the FDE use case. That is a good point though, maybe you are right that initramfs implementation is better since it would be of greater use to more people. I guess you also could have parking heads w/ a multi-disk setup if one is not being accessed on boot. My laptop has one HDD and one SDD, so I wasn't thinking about that either.

As far as a vendor utility, I think it would probably be best to try and stay away from anything propritary like that.

Regarding the udev rule, I am aware of the cons of using that method. Hence, I was willing to try your little package here. I think that I would just not run another daemon on my system if the only thing I am going to be using it for is setting the APM. This is especially the case with my awareness of alternative solutions. I have nothing against upower and if I had more uses for it, I would probaby consider it.

Anyway, thanks again, I will keep you posted if I discover any news that may help.

WonderWoofy commented on 2012-10-02 21:24

BTW, are you the one who started up the conversation about /usr/lib/systemd/system-sleep hooks and APM in Arch General (Marcos)? If not, you should be aware that there is a conversation (and trolling) going on there at the moment.

R00KIE commented on 2012-10-02 20:18

I was trying to avoid using an udev rule since it's harder to debug, the typical use case (I guess) is going to be to set the APM of the internal drive that comes with laptops, otherwise an udev rule would be more appropriate.

Currently I am setting the APM level in the initramfs, for my case this helps avoid one head park for each cold boot or resume from hibernation. I'm using full disk encryption, so the time it takes to input the password and get it verified is enough to let the HD do a head park.

Regarding the discussion in Arch General, I am aware of it, I subscribe that list. From one of the posts I really get the sense that putting a script in /usr/lib/systemd/system-sleep is the way to go, the alternative is to use a vendor utility to set the APM level and store it in the firmware.

As for the default value of the APM level, 255 should be the value to use to disable APM completely (according to 'man hdparm'), some disks don't seem to support it but as you say at least yours falls back to 254 and I suppose that would be the case for other disks too, as with other things the user is responsible for checking any applicable configuration files and doing any customization deemed necessary.

WonderWoofy commented on 2012-10-02 19:47

BTW, are you the one who started up the conversation about /usr/lib/systemd/system-sleep hooks and APM in Arch General (Marcos)? If not, you should be aware that there is a conversation (and trolling) going on there at the moment.

WonderWoofy commented on 2012-10-02 18:04

Yeah, I think reliability is the key here. I know about upower's abilities, but I much prefer to simply create what I need, rather than unnecessarily load something to do a single simple task.

I think a better way to set APM early is a udev rule. I guess the initramfs would be earlier, but I figure that there is no reason to set it that early, as the system is actively using the hdd at that time. The way I had it set before I found your package here, is match a udev rule to the desired drive, and when found simly run the hdparm command. Works flawlessly.

I was then simply using the system-sleep directory to reset it on wake, like your system here.

I think it is a good start, maybe with a bit more practical experience with systemd, a better solution will some along. For now, I am glad you have made a working system here.