Package Details: systemd-hddapm 1.6-1

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: 13
Popularity: 0.000000
First Submitted: 2012-09-24 20:29
Last Updated: 2015-07-15 19:04

Latest Comments

R00KIE commented on 2013-06-01 11:25

You are right, there was no install message. I had the install file but forgot to add the install= line to the PKGBUILD. Package updated to show the install message.

stativ commented on 2013-06-01 09:08

R00KIE: There is no install message.

R00KIE commented on 2013-05-31 23:54

Did you try 'udevadm info -a -p $(udevadm info -q path -n /dev/sdx)' as stated in the install message?

diggit commented on 2013-05-31 11:23

Sorry, my bad. I had to re-enable it (disable, enable). Then was created missing symlink. One question, where to get correct identification string of device? (ATTRS{model}=="this string")

R00KIE commented on 2013-05-30 10:41

Did you try 'systemctl enable hddapm' and reboot?

diggit commented on 2013-05-29 16:41

My HDD has apm settings in default (128) after every wake up(when in was suspended). Is it possible to modify rule to set defined value after every wake up too?

diggit commented on 2013-05-29 16:26

My HDD has apm settings in default (128) after every wake up(when in was suspended). Is it possible to modify rule to set defined value after every wake up too?

R00KIE commented on 2013-05-25 20:10

This change makes the package more robust and flexible than it was before.

The package provides a rule that can be used as example, the install message explicitly says what the user should do and there is a wiki page about writing udev rules, there is enough information to point the user in the right direction.

PerfectGentleman commented on 2013-05-25 09:17

i should notice that editing udev rules is not simple for users

R00KIE commented on 2013-05-22 11:19

Yes, that is correct. You should edit the udev rule to match the hard disk you want to control. If you have more than one device just add more rules.

The benefit of using udev is that as devices show up they will be set to the proper APM level. This helps in the case where you use this in the initramfs and the hook runs too early and not all disks are ready and present yet.

Hot swapping, which I didn't consider initially should also work without problems.

All comments