run.Rserve makes the current R process into an Rserve
instance. Rserve takes over until it is shut down or receives a user
interrupt signal. The main difference between Rserve and
run.Rserve is that Rserve starts a new process, whereas
run.Rserve turns the current R session into Rserve. This is only
possible if there are no UI elements or other parts that could
interfere with the prepation of Rserve.
stop.Rserve stops currently running background servers.
This only applies to servers started using background=TRUE.
run.Rserve(..., config.file = "/etc/Rserve.conf", background = FALSE)
stop.Rserve()Returns TRUE after the Rserve was shut down.
all named arguments are treated as entries that would be otherwise
present in the configuration file. So argument foo="bar"
has the same meaning as foo bar in the configuration
file. The only exception is that logical values can be used instead
of enable/disable. Some settings such as uid are
not relevant and thus ignored.
path of the configuration file to load in the Rserve. It will be loaded before the above settings and is optional, i.e. if the file is not present or readable it will be ignored.
logical, the default FALSE starts the server and does
not return until all servers have been shut down - typically
in response to an interrupt. If this argument is set to
TRUE then the server is started in teh background of
this R session and control is returned immediately (currently
not supported on Windows). In that case requests will be only
processed if no other computation is running in R, but the
R console can be still used to modify the session.
Such background servers can be stopped with the
stop.Rserve function.
Simon Urbanek
Rserve