search for: pskill

For the record, I've just filed the following bug report with a patch to https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17395: tools::pskill() returns either random garbage or incorrect values, because the internal ps_kill() (a) it does not initiate the returned logical, and (b) it assigns the logical returned the 0/-1 value of C's kill(). # Example 1: returns garbage due to non-initiated allocation > as.integer(tools::pskill(0...

...by querying them for their Sys.getpid(), e.g. pids <- parallel::clusterEvalQ(cl, Sys.getpid()) Is there a function in core R for testing whether a process with a given PID exists or not? From trial'n'error, I found that on Linux: pid_exists <- function(pid) as.logical(tools::pskill(pid, signal = 0L)) returns TRUE for existing processes and FALSE otherwise, but I'm not sure if I can trust this. It's not a documented feature in ?tools::pskill, which also warns about 'signal' not being standardized across OSes. The other Linux alternative I can imagine is:...

...pids <- parallel::clusterEvalQ(cl, Sys.getpid()) > > > > Is there a function in core R for testing whether a process with a > > given PID exists or not? From trial'n'error, I found that on Linux: > > > > pid_exists <- function(pid) as.logical(tools::pskill(pid, signal = 0L)) > > > > returns TRUE for existing processes and FALSE otherwise, but I'm not > > sure if I can trust this. It's not a documented feature in > > ?tools::pskill, which also warns about 'signal' not being standardized > > across OSes. &...

...tpid(), e.g. > > pids <- parallel::clusterEvalQ(cl, Sys.getpid()) > > Is there a function in core R for testing whether a process with a > given PID exists or not? From trial'n'error, I found that on Linux: > > pid_exists <- function(pid) as.logical(tools::pskill(pid, signal = 0L)) > > returns TRUE for existing processes and FALSE otherwise, but I'm not > sure if I can trust this. It's not a documented feature in > ?tools::pskill, which also warns about 'signal' not being standardized > across OSes. > > The other Linux...

...unction to kill a process? I found one in package fork but it is specific to UNIX and I want something that also works on Windows. The XP console command, taskkill, will do it so I can easily get the effect but it won't work on other Windows systems, even 2000 and NT. I found a free utility pskill.exe by googling around that does work across 2000/NT/XP but was still wondering about something more general in R.

...rallel::clusterEvalQ(cl, Sys.getpid()) >>> >>> Is there a function in core R for testing whether a process with a >>> given PID exists or not? From trial'n'error, I found that on Linux: >>> >>> pid_exists <- function(pid) as.logical(tools::pskill(pid, signal = 0L)) >>> >>> returns TRUE for existing processes and FALSE otherwise, but I'm not >>> sure if I can trust this. It's not a documented feature in >>> ?tools::pskill, which also warns about 'signal' not being standardized >>>...

...Unknown error. upsmon - Poll UPS [ups at localhost] failed - Data stale. I've already reported earlier how I've been spammed with invisible (at least over RDP) message.exe processes. Ate all the system memory and caused massive hard disk swapping, system would have been lost to me if pskill didn't work. I've disabled 'WALL' in upsmon.conf to hopefully prevent that occurring again. There doesn't appear to be a way to stop the 'data stale' messages from upsmon using NOTIFYFLAG. I also never see commbad/nocomm messages, just 'data stale' (UPS unplu...

...umber generator now uses the process ID as well as the current time, just in case two R processes are launched very rapidly on a machine with low-resolution wall clock (some have a resolution of a second; modern systems have microsecond-level resolution). o New function pskill() in the tools package to send a terminate signal to one or more processes, plus constants such as SIGTERM to provide a portable way to refer to signals (since the numeric values are OS-dependent). o New function psnice() in the tools package to return or change the ...

...umber generator now uses the process ID as well as the current time, just in case two R processes are launched very rapidly on a machine with low-resolution wall clock (some have a resolution of a second; modern systems have microsecond-level resolution). o New function pskill() in the tools package to send a terminate signal to one or more processes, plus constants such as SIGTERM to provide a portable way to refer to signals (since the numeric values are OS-dependent). o New function psnice() in the tools package to return or change the ...