New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider relocating /usr/lib64/pm-utils/sleep.d/52qubes-pause-vms #3909

Open
mirrorway opened this Issue May 19, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@mirrorway

mirrorway commented May 19, 2018

Qubes OS version:

R4.0

Affected component(s):

qubes suspend handling


Steps to reproduce the behavior:

  1. want to install a sleep hook
  2. notice qubes calls /usr/lib64/pm-utils/sleep.d/52qubes-pause-vms
  3. great, I'll just create a sleep hook called 40my-sleep-hook and stick it there
  4. suspend

Expected behavior:

40my-sleep-hook runs before 52qubes-pause-vms

Actual behavior:

40my-sleep-hook does not run.

General notes:

It turns out /usr/lib/systemd/system/qubes-suspend.service directly runs 52qubes-pause-vms, and nothing else in that folder.

So sleep hooks have to be set up via systemd service file. Which is fine, but the naming and location of sleep.d/52qubes-pause-vms suggests otherwise.


Related issues:

@mirrorway mirrorway changed the title from Consider renaming/relocating /usr/lib64/pm-utils/sleep.d/52qubes-pause-vms to Consider relocating /usr/lib64/pm-utils/sleep.d/52qubes-pause-vms May 19, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.1 milestone May 19, 2018

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 27, 2018

Member

Yes, I think pm-utils is nowadays completely dead and replaced by systemd handling (at least on Fedora), so we can abandon this legacy location.

Member

marmarek commented May 27, 2018

Yes, I think pm-utils is nowadays completely dead and replaced by systemd handling (at least on Fedora), so we can abandon this legacy location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment