Using the Services Utility from a Command Line
When using the Services utility from a command line, note that:
Unlike in Dashboard use, you can stop services whose Type is Critical (service type is dened
in the user-modiable processinfo.xml le.)\
Prior to stopping a service, you should be aware of the signicance of stopping it, including
any dependant services that may be affected.
The Services utility will not allow you to stop services with peer or child dependencies while
those dependencies are running. If you attempt to stop such a service, the utility returns a
message stating that dependent services are running.
Table 5: Command Line Options
Example:Description:Command:
>cmdhelpDisplays a list of commands specic to this utility.cmdhelp, chelp
Note: Using Help or ? also displays this list, but includes several
additional ICM commands (e.g., echo, error_stop) not used by this
utility.
><command> /?Displays syntax for a specied command./?
><app_servername> /
<options>
Species the system on which the utility should run. If not
specied, the utility is run on the local system.
appserver
> /system <host_name> /
<options>
Species the target system the utility should run against. If not
specied, the utility is run against the local system.
system
>localhostSets the network address of name of the target node to the local
host.
localhost
Note: By default, unless a different system is specied (using the
system command) the local host is assumed to be the target system.
>listDisplays information on all services on the target system.list
ORFor each service, this command displays:
Service Name: The service's name. >list
<localfile_path\filename>
PID: The service's process ID.
Type: Critical, Known, or Unknown, as dened in the target
system's processinfo.xml le.
Start (if the process is stopped) or Stop (if the process if started.
Cisco Support Tools User Guide for Cisco Unified Software Release 2.1(1)
129
Chapter 12: Using Cisco Tools from a Command Line
How to Use the Services Utility from a Command Line