| Line 112... |
Line 112... |
| 112 |
}
|
112 |
}
|
| 113 |
|
113 |
|
| 114 |
Function \code{makeForkCluster} creates a socket cluster by forking
|
114 |
Function \code{makeForkCluster} creates a socket cluster by forking
|
| 115 |
(and hence is not available on Windows). It supports options
|
115 |
(and hence is not available on Windows). It supports options
|
| 116 |
\code{port}, \code{timeout} and \code{outfile}, and always uses
|
116 |
\code{port}, \code{timeout} and \code{outfile}, and always uses
|
| 117 |
\code{useXDR = FALSE}. See \code{\link{mcfork}} for the inadvisability of using
|
117 |
\code{useXDR = FALSE}. It is \emph{strongly discouraged} to use the
|
| 118 |
the \code{"FORK"} cluster with GUI front-ends and multi-threaded libraries.
|
118 |
\code{"FORK"} cluster with GUI front-ends or multi-threaded libraries.
|
| - |
|
119 |
#ifdef unix
|
| - |
|
120 |
See \code{\link{mcfork}} for details.
|
| - |
|
121 |
#endif
|
| 119 |
|
122 |
|
| 120 |
It is good practice to shut down the workers by calling
|
123 |
It is good practice to shut down the workers by calling
|
| 121 |
\code{\link{stopCluster}}: however the workers will terminate
|
124 |
\code{\link{stopCluster}}: however the workers will terminate
|
| 122 |
themselves once the socket on which they are listening for commands
|
125 |
themselves once the socket on which they are listening for commands
|
| 123 |
becomes unavailable, which it should if the master \R session is
|
126 |
becomes unavailable, which it should if the master \R session is
|