Launching a daemon is very much akin to launching a satellite. They are a way
to deploy a daemon (in our case) on the desired machine. Once it executes, it
connects back to the host process using its own communications.
launch_local
deploys a daemon on the local machine in a new
background Rscript
process.
launch_remote
returns the shell command for deploying daemons as a
character vector. If an ssh_config()
, cluster_config()
or
remote_config()
configuration is supplied then this is used to launch the
daemon on the remote machine.
Usage
launch_local(n = 1L, ..., .compute = NULL)
launch_remote(n = 1L, remote = remote_config(), ..., .compute = NULL)
Arguments
- n
integer number of daemons.
or for
launch_remote
only, a 'miraiCluster' or 'miraiNode'.- ...
(optional) arguments passed through to
daemon()
. These includeasycdial
,autoexit
,cleanup
,output
,maxtasks
,idletime
, andwalltime
. Only supply to override arguments originally provided todaemons()
, otherwise those will be used instead.- .compute
character value for the compute profile to use (each has its own independent set of daemons), or NULL to use the 'default' profile.
- remote
required only for launching remote daemons, a configuration generated by
ssh_config()
,cluster_config()
, orremote_config()
. An emptyremote_config()
does not perform any launches but returns the shell commands for deploying manually on remote machines.
Value
For launch_local: Integer number of daemons launched.
For launch_remote: A character vector of daemon launch commands, classed as 'miraiLaunchCmd'. The printed output may be copy / pasted directly to the remote machine.
Details
Daemons must already be set for launchers to work.
These functions may be used to re-launch daemons that have exited after reaching time or task limits.
For non-dispatcher daemons using the default seed strategy, the generated
command contains the argument rs
specifying the length 7 L'Ecuyer-CMRG
random seed supplied to the daemon. The values will be different each time
the function is called.