Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-04-23 Thread Ralf Jung
Hi, > This doesn't guarantee that the service is run on resume. > Those targets are activated on suspend/hibernate, so there is a race and > you might actually run /usr/lib/pm-utils/power.d/95hdparm-apm *before* > the system is suspended. You'd have to order this service after the > *service* whic

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-04-21 Thread Chris
Am Tue, 21 Apr 2015 14:53:36 +0200 schrieb Michael Biebl : > This doesn't guarantee that the service is run on resume. Many thanks for your help in solving this, Michael! (Unfortunately, I had only tried the imperfect unit file, and I had just luck (or not) so that I did not see it fail.) --

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-04-21 Thread Michael Biebl
On Wed, 25 Dec 2013 17:33:04 +0100 Ralf Jung wrote: > Dear maintainer, > > adding the attached systemd unit fixes restoring the hdparm > configuration when systemd is used. I'd appreciate if you could add this > (or a similar solution) to the package. This proposed patch doesn't work as-is, due

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-03-04 Thread Ralf Jung
Hi, > The specific one you posted above could probably use "oneshot": > > [Service] > Type=oneshot Thanks! I'm not sure if I want anything to wait for hdparm being done with this (which seems to be the only consequence), but in any case it sounds more appropriate to what that unit is doing. Kin

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-03-04 Thread Chris
> I don't know whether udev just doesn't trigger > after a resume Either a generic systemd unit file is required to trigger an udev change event http://bugs.debian.org/779412, or a hdparm specific one to trigger just the hdparm script. The specific one you posted above could probably use "oneshot

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-03-01 Thread Ralf Jung
Hi again, sorry for the noise. This is just to confirm that there simply is no event for the disks on resume: > $ sudo udevadm monitor -uk > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[49453.633

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-03-01 Thread Ralf Jung
Hi again, I did some quick debugging, and it seems like the script /lib/udev/hdparm is never even run on suspend-resume. I'm not really familiar with udev, so I don't know whether udev just doesn't trigger after a resume, or whether there's some other problem here. The second mail in this bug con

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-02-26 Thread Ralf Jung
Hi, > I just uploaded 9.43-2 with the patch mentioned in this bug report. However, > I lack the hardware to test hdparm. So please test it before I file an > unblock request. This doesn't seem to work: After suspend-resume, my disk behaves as if hdparm was not run at all. I did not yet investigat

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2015-02-24 Thread Michael Meskes
I just uploaded 9.43-2 with the patch mentioned in this bug report. However, I lack the hardware to test hdparm. So please test it before I file an unblock request. Also I'm not sure if it's a wise idea to remove the init file at this stage of the release. Thanks. Michael -- Michael Meskes Mic

Bug#725284: hdparm + systemd: Patch to restore configuration after resume

2014-12-22 Thread Jonathan Michalon
On Wed, 25 Dec 2013 17:33:04 +0100 Ralf Jung wrote: > adding the attached systemd unit fixes restoring the hdparm > configuration when systemd is used. I'd appreciate if you could add this > (or a similar solution) to the package. I second this (works for me), although I suppose it would be even