Sudo systemctl vs pm suspend. d directories. systemd-suspend reads its configuration from the /etc/systemd/sleep. The user will then be able to use the sudo systemctl commands (e. systemctl hybrid-sleep suspends the system both to RAM and disk, so a complete power loss does not result in lost data. conf file (or files in a sleep. See the System Commands section in systemctl(1). pm-utils reads its configuration from files in /etc/pm/config. What is the best way to change the default behaviour of the GUI suspend button and closing the lid to use pm-suspend instead of the systemctl suspend? systemd does not use pm-utils to put the machine to sleep when using systemctl suspend, systemctl hibernate or systemctl hybrid-sleep; pm-utils hooks, including any custom hooks, will not be run. systemctl suspend-then-hibernate initially suspends the system to RAM as long as possible, then wakes it with an RTC alarm and hibernates. The commands are exactly what you'd expect: $ sudo systemctl suspend $ sudo systemctl hibernate $ sudo systemctl hybrid-sleep. d directory) and executes hooks from /usr/lib/systemd/system-sleep/ . You can also suspend and hibernate the system by using the systemctl command. d and /usr/lib/pm-utils/sleep. Use the GUI Update: on older versions of Ubuntu, it's possible that sudo systemctl suspend will not also lock the screen and require a password upon waking up, whereas my sudo true && gnome-screensaver-command -l && sudo pm-suspend command will always lock the screen first and require a password after wake-up. This mode is also called suspend to both. The systemctl hybrid-sleep command both suspends and hibernates the system. d and executes hooks from both /etc/pm/sleep. See the System Commands section in systemctl(1) pm-utils reads its configuration from files in /etc/pm/config. sudo pm-suspend everything works fine. g. conf. sudo systemctl poweroff, sudo systemctl reboot, sudo systemctl suspend and sudo systemctl hibernate). nuggmudbuhdglpibrmipkymmzcemzvxbakydejteqdphl