2 .\" Copyright (c) 2017 Peter Tribble
3 .\" Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH PMCONFIG 1M "May 1, 2017"
9 pmconfig \- Configure the Power Management system
13 \fB/usr/sbin/pmconfig\fR [\fB-r\fR]
18 The \fBpmconfig\fR utility sets the Power Management and suspend-resume
19 configuration. User has permission to change Power Management configuration
20 using \fBpmconfig\fR only if he is allowed to do so according to
21 \fBPMCHANGEPERM\fR keyword of \fB/etc/default/power\fR. User has permission to
22 change the suspend-resume configuration using \fBpmconfig\fR only if he is
23 allowed to do so according to the \fBCPRCHANGEPERM\fR keyword of
24 \fB/etc/default/power\fR. See FILES section below for a description of the
25 \fBPMCHANGEPERM\fR and \fBCPRCHANGEPERM\fR keywords of
26 \fB/etc/default/power\fR.
29 Based on user permissions, \fBpmconfig\fR first resets the Power Management
30 and/or suspend-resume state back to its default and then reads the new
31 Power Management and/or suspend-resume configuration from
32 \fB/etc/power.conf\fR and issues the commands to activate the new
33 configuration. The \fBpmconfig\fR utility is run at system boot. This utility
34 can also be run from the command line after manual changes have been made to
35 the \fB/etc/power.conf\fR file. For changes made to the
36 \fB/etc/power.conf\fR file to take effect, users must run \fBpmconfig\fR.
39 The following options are supported:
46 Reset Power Management and suspend-resume state to default and exit. User
47 must have both Power Management and suspend-resume configuration permission
53 The following exit values are returned:
60 Upon successful completion
75 \fB\fB/etc/power.conf\fR\fR
78 System Power Management configuration file.
84 \fB\fB/etc/default/power\fR\fR
87 File that controls permissions for system's Power Management and
88 suspend-resume features. The \fBPMCHANGEPERM\fR keyboard controls the Power
89 Management configuration permissions, while the \fBCPRCHANGEPERM\fR keyword
90 controls the suspend-resume configuration permissions.
102 Any user can change the configuration.
111 No one except super-user can change the configuration.
117 \fB\fB<user1, user2,...>\fR\fR
120 A user in this user list or a super-user can change the configuration. The
121 user list is a space and/or comma (,) separated list. You must enclose the list
122 in < and > characters.
128 \fB\fBconsole-owner\fR\fR
131 A user who owns the system console device node or a super-user can change the
137 The default values are \fBPMCHANGEPERM=console-owner\fR and
138 \fBCPRCHANGEPERM=console-owner\fR.
141 See \fBattributes\fR(5) for descriptions of the following attributes:
149 ATTRIBUTE TYPE ATTRIBUTE VALUE
151 Interface Stability Unstable
156 \fBsvcs\fR(1), \fBpowerd\fR(1M), \fBpower.conf\fR(4), \fBsvcadm\fR(1M),
157 \fBattributes\fR(5), \fBsmf\fR(5), \fBcpr\fR(7), \fBpm\fR(7D)
160 \fIUsing Power Management\fR
163 The \fBpmconfig\fR service is managed by the service management facility,
164 \fBsmf\fR(5), under the service identifier:
168 svc:/system/power:default
175 Administrative actions on this service, such as enabling, disabling, or
176 requesting restart, can be performed using \fBsvcadm\fR(1M). The service's
177 status can be queried using the \fBsvcs\fR(1) command.
180 If the program cannot open the configuration file, it prints an error message
181 to standard error. If the program encounters a syntax error in the
182 configuration file, it prints an error message and the line number of the error
183 in the configuration file. It then skips the rest of the information on that
184 line and processes the next line. Any configuration information already
185 processed on the line containing the error is used. If user does not have
186 permission to change Power Management and/or suspend-resume configuration, and
187 configuration file has entries for which user doesn't have permission, it
188 process the entries for which user has permissions and prints error on rest.