Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Using Git to Track


Git is a free and open source distributed version control system. The PSM server installation automatically creates a Git repository for /var/local/ems9001/conf and automatically adds the file to that repository. This allows you to track all updates to that file.

Every time you update the file, issue a git commit command and indicate the reason for the update. For example:

The text in quotations is freeform, and is used to specify the reason for the update and to identify the user who is making the change.

Here is a sample output of the git commit command:

To view the log of changes, use the git log command. For example:

This produces a log of all the changes made to the file, with the most recent change listed first:

To view the log of changes and their differences, use the git log -u <start>..<end> command. If <end> is omitted, the log will include all changes from <start> up to the most recent update. In this example, to view a log of all changes after installation:

This command shows the log of changes and their differences starting from the commit identifier 6835ba91cce1b8a8f2c5414315fc035b6e7545c8, which in this example is immediately after installation. The output is as follows:

In the above example, at 14:20:25, changed pm.historical.collectionEnabled to true, and at 14:22:56, changed schedule.neDbBackup.cron to be at 3:15 every morning.

If you have forgotten whether you have performed a git commit or not, use the git status command to check the status. For example:

The above output tells you that the file has been modified but not committed.

For more information on Git, see