Difference between revisions of "Migrate"
From MosixWiki
(New page: MIGRATE(M1) MOSIX Commands MIGRATE(M1) '''NAME''' MIGRATE - Manual control of running MOSIX processes '''SYNOPSIS''' migrate {{pi...) |
(No difference)
|
Latest revision as of 16:31, 7 November 2007
MIGRATE(M1) MOSIX Commands MIGRATE(M1) NAME MIGRATE - Manual control of running MOSIX processes SYNOPSIS migrate {{pid}|-j{jobID}} {node-number|IP-address|host} migrate {{pid}|-j{jobID}} home migrate {{pid}|-j{jobID}} out migrate {{pid}|-j{jobID}} freeze migrate {{pid}|-j{jobID}} continue migrate {{pid}|-j{jobID}} checkpoint migrate {{pid}|-j{jobID}} chkstop migrate {{pid}|-j{jobID}} chkexit DESCRIPTION Migrate {pid} manually migrates or otherwise affects a given MOSIX pro- cess (pid). Migrate -j{jobID} does the same to all of the user's processes with the given jobID (see mosrun(1)). The first option ({node-number|IP-address|host}) specifies a recommended target node to which to migrate the process(es). Note that no error is returned if MOSIX ignores this recommendation. The home option forces the process(es) to migrate back to its home-node. The out option forces a guest process(es) to move out of this node (this option is available only to the Super-User, The freeze option freezes the process(es) (guest processes may not be frozen). The continue option unfreeze the process(es). The checkpoint option requests the process(es) to take a checkpoint. The chkstop option requests the process(es) to take a checkpoint and stop: the process(es) may then be resumed with SIGCONT. The chkexit option requests the process(es) to take a checkpoint and exit. Migrate sends the instruction, but does not wait until the process(es) respond to it (or reject it). Except for the Super-User, one can normally migrate or affect only their own processes. The rule is: if you can kill it, you are also allowed to migrate/affect it. The best way to locate and find the PID of MOSIX processes is by using mosrun(1), mosps(1). SEE ALSO mosps(1), mosix(7). MOSIX May 2006 MOSIX