File Configuration

Power Manager's Scheduler provides a method of updating the configuration through Property List, `.plist` files. This method can be used to distribute schedules, licence codes, and other settings where access to the Mac is restricted.

On launch, Power Manager’s Scheduler looks for a configuration file in a specific location. If the file exists, and has changed since the last launch, then the enclosed set of requests are issued.

The configuration file can contain any valid pmdctl API request. This allows a configuration file to set up Power Manager precisely as desired, without needing a network connection.

File configuration location:

/Library/Application Support/Power Manager/Configuration/pmd.plist

The pmd.plist file is checked and loaded at launch.

We use the File Configuration method to support the creation of installers containing custom schedules and licence details.


To ensure Power Manager’s security, the configuration file and the location must have specific ownership and access permissions set. The Scheduler will not use a configuration file unless the security requirements are met:

The file configuration permissions and file layout must match:

drwxr-xr-x root:wheel Configuration
-rw-r----- root:wheel Configuration/pmd.plist

Use the following shell script to set the correct parent directory and file permissions:

cd '/Library/Application Support/Power Manager/'

sudo mkdir Configuration
sudo cp ~/Desktop/pmd.plist Configuration/.

sudo chown -R root:wheel Configuration
sudo chmod 640 Configuration/pmd.plist
sudo chmod 755 Configuration

Applying a Configuration File

The configuration file is automatically checked and applied when Power Manager’s Scheduler is launched. This normally occurs when the Mac is powered on or restarted.

To avoid needing to restart the Mac each time the configuration file is updated, Power Manager’s Scheduler supports a manual alternative.

The Scheduler can be asked to check the configuration file by sending a Hang Up (HUP) signal. HUP is a UNIX signal. On receiving a HUP signal, the Scheduler will check the configuration file for changes, and apply the contents if appropriate.

Below is a shell command for sending a Hang Up (HUP) signal to the process:

sudo killall -HUP

We support this method to create configuration only installers that do not need a restart.

File Format

The configuration file is binary or XML Property List formatted. The file’s root object must be an array.

The array contains dictionary items. Each dictionary item represents an API request.

The request dictionary has only two entries:

Request Dictionary Format
requeststringAPI request
parametersdictionaryparameter key/value pairs (optional)

Each request dictionary in the configuration file is read, encoded as an API request, and issued. If a request fails, the remaining requests in the configuration file are skipped.

Below is an example configuration file containing two requests:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "">
<plist version="1.0">