Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #977
Difficulty: Medium
A Linux Kernel Code of Conflict was introduced on 8 March 2012.
True or False?
Linux & Unix Commands - Search Man Pages

pm-is-supported(1) [centos man page]

PM-IS-SUPPORTED(1)					       pm-utils User Manual						PM-IS-SUPPORTED(1)

pm-is-supported - Test whether suspend or hibernate is supported. SYNOPSIS
pm-is-supported [{--suspend | --hibernate | --suspend-hybrid}] DESCRIPTION
This manual page documents briefly the pm-is-supported command. The intended purpose of pm-is-supported is to find out which power management modes are supported by the system. hald(8) will call it to do just that. (Note that UPower does not use this.) OPTIONS
--suspend Test whether suspend is supported. Suspend is a state where most devices are shutdown, except for RAM. This state still draws power. --hibernate Test whether hibernate is supported. During hibernate the state of the system is saved to disk, the system is fully powered off. --suspend-hybrid Test whether hybrid-suspend is supported. Hybrid-suspend is the process where first the state of the system is saved to disk -- just like with hibernate -- but instead of poweroff, the system goes in suspend state, which means it can wakeup quicker than for normal hibernation. The advantage over suspend is that you can resume even if you run out of power. s2both is a hybrid-suspend implementation. RETURN VALUE
The result of the test for a certain powermanagement state is defined by the following exit codes. Code Diagnostic 0 State available. 1 State NOT available. SEE ALSO
hald(8), pm-suspend(8), s2both(8), UPower(7) AUTHOR
Tim Dijkstra <> Manpage author. COPYRIGHT
Copyright (C) 2007 Tim Dijkstra This manual page was originally written for the Debian(TM) system, and has been adopted by the pm-utils project. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation. pm-is-supported Apr 18, 2007 PM-IS-SUPPORTED(1)

Check Out this Related Man Page

SYSTEMD-SUSPEND.SERVICE(8)				      systemd-suspend.service					SYSTEMD-SUSPEND.SERVICE(8)

systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, systemd-suspend-then-hibernate.service, systemd-sleep - System sleep state logic SYNOPSIS
systemd-suspend.service systemd-hibernate.service systemd-hybrid-sleep.service systemd-suspend-then-hibernate.service /lib/systemd/system-sleep DESCRIPTION
systemd-suspend.service is a system service that is pulled in by and is responsible for the actual system suspend. Similarly, systemd-hibernate.service is pulled in by to execute the actual hibernation. Finally, systemd-hybrid-sleep.service is pulled in by to execute hybrid hibernation with system suspend and pulled in by to execute system suspend with a timeout that will activate hibernate later. Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units, respectively) will run all executables in /lib/systemd/system-sleep/ and pass two arguments to them. The first argument will be "pre", the second either "suspend", "hibernate", "hybrid-sleep", or "suspend-then-hibernate" depending on the chosen action. Immediately after leaving system suspend and/or hibernation the same executables are run, but the first argument is now "post". All executables in this directory are executed in parallel, and execution of the action is not continued until all executables have finished. Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are intended for local use only and should be considered hacks. If applications want to react to system suspend/hibernation and resume, they should rather use the Inhibitor interface[1]. Note that systemd-suspend.service, systemd-hibernate.service, and systemd-hybrid-sleep.service systemd-suspend-then-hibernate.service should never be executed directly. Instead, trigger system sleep states with a command such as "systemctl suspend" or similar. Internally, this service will echo a string like "mem" into /sys/power/state, to trigger the actual system suspend. What exactly is written where can be configured in the "[Sleep]" section of /etc/systemd/sleep.conf or a sleep.conf.d file. See systemd-sleep.conf(5). OPTIONS
systemd-sleep understands the following commands: -h, --help Print a short help text and exit. --version Print a short version string and exit. suspend, hibernate, hybrid-sleep, suspend-then-hibernate Suspend, hibernate, suspend then hibernate, or put the system to hybrid sleep. SEE ALSO
systemd-sleep.conf(5), systemd(1), systemctl(1), systemd.special(7), systemd-halt.service(8) NOTES
1. Inhibitor interface systemd 237 SYSTEMD-SUSPEND.SERVICE(8)

Featured Tech Videos