Displaying 2 results from an estimated 2 matches for "setuptimeout".
Did you mean:
setup_timeout
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
2019 Mar 18
2
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
...:
port 80 cannot be opened
The launched R worker is still running:
$ ps aux | grep -E "exec[/]R"
hb 20778 37.0 0.4 283092 70624 pts/0 S 17:50 0:00
/usr/lib/R/bin/exec/R --slave --no-restore -e parallel:::.slaveRSOCK()
--args MASTER=localhost PORT=80 OUT=/dev/null SETUPTIMEOUT=120
TIMEOUT=2 592000 XDR=TRUE
This process will keep running for 'TIMEOUT=2592000' seconds (= 30
days). The reason for this is that it is currently in the state where
it attempts to set up a connection to the main R process:
> parallel:::.slaveRSOCK
function ()
{
makeSOCKm...
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
2019 Mar 27
0
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
...;
> The launched R worker is still running:
>
> $ ps aux | grep -E "exec[/]R"
> hb 20778 37.0 0.4 283092 70624 pts/0 S 17:50 0:00
> /usr/lib/R/bin/exec/R --slave --no-restore -e parallel:::.slaveRSOCK()
> --args MASTER=localhost PORT=80 OUT=/dev/null SETUPTIMEOUT=120
> TIMEOUT=2 592000 XDR=TRUE
>
> This process will keep running for 'TIMEOUT=2592000' seconds (= 30
> days). The reason for this is that it is currently in the state where
> it attempts to set up a connection to the main R process:
>
> > parallel:::.slaveRSOCK...