Killing OOMMF Processes: killoommf
Keywords: userguide

Next: Last Oxsii/Boxsi run: lastjob Up: Command Line Utilities Previous: Cyclic Redundancy Check: crc32

##
Killing OOMMF Processes: killoommf

The killoommf application terminates running OOMMF processes.

Launching
The killoommf command line is:

    tclsh oommf.tcl killoommf [standard options] [-account name] \
       [-hostport port] [-pid] [-q] [-show] [-shownames] [-test] \
       [-timeout secs] 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.
`-pid`
  Select processes by system pid rather than OOMMF oid.
`-q`
  Quiet; don't print informational messages.
`-show`
  Don't kill anything, just print matching targets.
`-shownames`
  Don't kill anything, just print nicknames of matching targets, where nicknames are as set by the MIF 2.1 `Destination` command.
`-test`
  Don't kill anything, just test that targets are responding.
`-timeout secs`
  Maximum time to wait for response from servers, in seconds. Default is five seconds.
`oid ...`
  List of one or more oids (OOMMF ID's), application names, nicknames, or the keyword ``all''. Glob-style wildcards may also be used. This field is required (there are no default kill targets). If the `-pid` option is specified then numbers are interpreted as referring to system process ID's rather than OOMMF ID's.

The killoommf command affects processes that listen to OOMMF message traffic. These are the same applications that are listed in the ``Threads'' list of mmLaunch. The command

    tclsh oommf.tcl killoommf all

is essentially equivalent to the ```File|Exit All OOMMF`'' menu option in mmLaunch, except that killoommf does not shut down any mmLaunch processes.

An OOMMF application that does not respond to killoommf can be killed by using the OOMMF command line program pidinfo to determine its PID (process identification) as used by the operating system, and then using the system facilities for terminating processes (e.g., `kill` on Unix, or the `Windows Task Manager` on Windows).

OOMMF Documentation Team
September 29, 2018