Displaying 3 results from an estimated 3 matches for "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()
...s 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 ()
{
makeSOCKmaster <- function(master, port, setup_timeout, timeout,
useXDR) {
...
repeat {
con <- tryCatch({
socketConnection(master, port = port, blocking = TRUE,
open = "a+b", timeout = timeout)
}, error = identity)
...
}
In other words, it is...
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()
...IMEOUT=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 ()
> {
> makeSOCKmaster <- function(master, port, setup_timeout, timeout,
> useXDR) {
> ...
> repeat {
> con <- tryCatch({
> socketConnection(master, port = port, blocking = TRUE,
> open = "a+b", timeout = timeout)
> }, error = ident...
2008 Jan 01
1
Redundant timers
Hello.
I am on an irrational crusade against unneeded timers (it started as a
well-meaining power saving exercise), and I have now started removing
polling in Dovecot.
Attached is a patch with the work I did on this the other night. Would
something like that be acceptable, or should I make it in a different
way?
There seems to be no one-shot timer support, right?
Is there a Dovecot coding