Example:Description:Command:
>stop <pid> <process_name>Terminates a started process on the target system.kill
>saveSaves the latest list command results to a processes file in the
application server's Repository.
save
OR
Saved output is stored as XML-formatted text. >save <filename>
If no file name is specified, output is saved to a file named:
Processes list <host_name> <timestamp>.xml.
Optionally, you can include an argument that specifies a file name.
>filesDisplays the list of precesses files in the application server's
Repository.
files
>view <filename>Displays the contents of a precesses file from the Repository on
the application server.
view
OR
>view <filename>
<localfile_path\filename>
>remove <filename>Deletes a specified precesses file from the Repository on the
application server.
remove, rm
>rename <filename>
<new_filename>
Renames a precesses file in the Repository on the application
server.
rename, ren
>read <filename>Directs command input to another input file.read_file, read
For example, you can direct input to run a batch file that contains
a series of commands executable by this utility.
><command> /silentExecutes command without displaying output.silent
Note: Available in command-line mode only.
>quitEnds the program.quit, q
Viewing and Killing a Service - ExamplesThe following table shows an example of viewing and killing a process, with a description of
each entry.
Description:Command Option:
Invokes the Processes utility.>processcontrol
Cisco Support Tools User Guide for Cisco Unified Software Release 2.1(1)
133
Chapter 12: Using Cisco Tools from a Command Line
How to Use the Processes Utility from a Command Line