Next: Platform-Independent Make: pimake
Up: Command Line Utilities
Previous: Oxs regression tests: oxsregression
OOMMF and Process ID Information: pidinfo
The pidinfo command prints a table mapping OOMMF ID's (OID's)
to system process ID's (PID's) and application names.
Launching
The pidinfo command line is:
tclsh oommf.tcl pidinfo [standard options] [-account name] \
[-hostport port] [-names] [-noheader] [-pid] [-ports] \
[-timeout secs] [-wait secs] [-v] [oid ...]
where
- -account name
- Specify the account name. The default is the same used by
mmLaunch:
the current user login name, except on Windows 9X, where the dummy
account ID ``oommf'' may be used
instead.
- -hostport port
- Use the host server listening on port. Default is set by the
Net_Host port setting in oommf/config/options.tcl, or by
the environment variable OOMMF_HOSTPORT (which, if set,
overrides the former). The standard setting is 15136.
- -names
-
Display application nicknames, which are used by the MIF 2.1
Destination
command.
- -noheader
- Don't print column headers.
- -pid
- Select processes by system pid rather than OOMMF oid.
- -ports
- Display active server ports for each application.
- -timeout secs
- Maximum time to wait for response from servers, in seconds. Default
is five seconds.
- -v
- Display information about the host and account servers.
- -wait secs
- If no match is found, then retry for up to secs seconds. Default
is zero seconds, i.e., try once.
- oid ...
- List of OOMMF ID's to display information about. Default is all
current applications. If the -pid option is specified then this
selection is by system process ID's rather than OOMMF ID's.
The title bar of running OOMMF applications typically displays the
application OID, which are used by OOMMF applications to identify one
another. These ID's start at 0 and are incremented each time a newly
launched application registers with the account server. The OID's are
independent of the operating system PID's. The PID is needed to obtain
information, e.g., resource use, about a running process using system
utilities. The PID may also be needed to invoke the operating system
``kill'' facility to terminate a rogue OOMMF application. The
pidinfo application can be used to correspond OID's or OOMMF application names to PID's for such purposes.
OOMMF Documentation Team
September 28, 2017