Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: How to Build Manifests for Managed Hosts (Command Line)
- Next: How to Get the Software Status of Managed Hosts (Command Line)

## How to Audit Managed Hosts (Command Line)

The baseline manifest does not need to be built on the managed host. You can build a baseline manifest on a master system before creating the Solaris Flash archive.

1. Determine which managed hosts you want to audit.

   For example, audit the `/web-server/host1` and `/web-server/host2` managed hosts.

2. Audit managed hosts.

       $ changemgr audit [ -u username ] [ -p file ] [ -d domain ] \
       -o relfilepath.txt [ -r relfilepath.brul ] relfilepath.bmft topopath ...

   `-o` `relfilepath.txt`

     Specifies where to write the report on manifest differences.

   `-r` `relfilepath.brul`

     Specifies the audit rules file to use to create the manifest.

   `relfilepath.bmft`

     Specifies the path to the manifest file that is relative to the top of the Change Manager repository.

   topopath

     Specifies the path to a managed host or host group that is relative to the top of the selected administrative domain.

   For descriptions of the other options, see How to Build Manifests for Managed Hosts (Command Line).

### Example—Auditing Managed Hosts

Suzi audits the `/web-server/host1` managed host. She stores the report in the `/web-server/usr-only.txt` file. She audits the managed host by comparing its manifest against the baseline manifest called `/web-server/baseline.bmft`.

    $ changemgr audit suzi \
    -o /web-server/usr-only.txt -r usr-only.brul \
    /web-server/baseline.bmft /web-server/host1

To understand how to interpret the report results, see Comparison Report Format.

- Previous: How to Build Manifests for Managed Hosts (Command Line)
- Next: How to Get the Software Status of Managed Hosts (Command Line)

- © 2010, Oracle Corporation and/or its affiliates