search for: forked

I was looking at the CRAN package 'bfork-0.1.2', which exposes the Unix fork() and waitpid() calls at the R code level, and noticed that the help file example for bfork::fork removes R's temporary directory, the value of tempdir(). I think it happens because the forked process shares the value of tempdir() with the parent process and removes it when it exits. This seems like a serious problem - should 'check' make sure that running code in a package's examples, vignettes, etc. leaves tempdir() intact? > dir.exists(tempdir()) [1] TRUE > library...

...ba: tfork waiter process +-4346 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground +-4347 samba: tfork waiter process +-4348 samba: task[nbt] pre-fork master +-4349 samba: tfork waiter process +-4350 samba: task[rpc] pre-forked worker(0) +-4351 samba: tfork waiter process +-4352 samba: task[rpc] pre-forked worker(1) +-4353 samba: tfork waiter process +-4354 samba: task[wrepl] pre-fork master +-4355 samba: tfork waiter process +-4356 samba: task[rpc] p...

...he parallel package. Cheers, Simon > On Jan 10, 2020, at 10:58 AM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > > The RStudio GUI was just one example. AFAIK, and please correct me if > I'm wrong, another example is where multi-threaded code is used in > forked processing and that's sometimes unstable. Yes another, which > might be multi-thread related or not, is > https://stat.ethz.ch/pipermail/r-devel/2018-September/076845.html: > > res <- parallel::mclapply(urls, function(url) { > download.file(url, basename(url)) > }) >...

ISSUE: Using *forks* for parallel processing in R is not always safe. The `parallel::mclapply()` function uses forked processes to parallelize. One example where it has been confirmed that forked processing causes problems is when running R via RStudio. It is recommended to use PSOCK clusters (`parallel::makeCluster()`) rather than *forked* processes when running R from RStudio ( https://github.com/rstudio/rstudi...

...1/10/20 7:33 AM, Henrik Bengtsson wrote: >> I'd like to pick up this thread started on 2019-04-11 >> (https://hypatia.math.ethz.ch/pipermail/r-devel/2019-April/077632.html). >> Modulo all the other suggestions in this thread, would my proposal of >> being able to disable forked processing via an option or an >> environment variable make sense? > > I don't think R should be doing that. There are caveats with using fork, and they are mentioned in the documentation of the parallel package, so people can easily avoid functions that use it, and this all has be...

...that's what pthread_atfork() is for. Most libraries don't allow duplicated fds or have rules about thread safety, so it is your responsibility in the package to abide by those rules if you want it to function after forking. Some libraries don't allow forking at all, e.g., JVMs cannot be forked (because they are too complex to make them fork-safe). In general, you cannot assume that (non-R) code is fork-safe unless it has been designed to be. That's why mcparallel() should only be used for pure R code (and even that is with I/O limitations) and C code that is explicitly fork-safe. As...

...>>> On Jan 10, 2020, at 10:58 AM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: >>> >>> The RStudio GUI was just one example. AFAIK, and please correct me if >>> I'm wrong, another example is where multi-threaded code is used in >>> forked processing and that's sometimes unstable. Yes another, which >>> might be multi-thread related or not, is >>> https://stat.ethz.ch/pipermail/r-devel/2018-September/076845.html: >>> >>> res <- parallel::mclapply(urls, function(url) { >>> download...

I have been using the fork package on a cluster to spawn jobs. I have noticed that I end up with many "R defunct" (zombie) processes following the use of fork that do not die completely until I close down R. Initially, I thought it may be my code but I ran the example from the latest fork package (see code below) on R.2.3.1 and ended up with the same problem. The code from the

I'd like to pick up this thread started on 2019-04-11 (https://hypatia.math.ethz.ch/pipermail/r-devel/2019-April/077632.html). Modulo all the other suggestions in this thread, would my proposal of being able to disable forked processing via an option or an environment variable make sense? I've prototyped a working patch that works like: > options(fork.allowed = FALSE) > unlist(parallel::mclapply(1:2, FUN = function(x) Sys.getpid())) [1] 14058 14058 > parallel::mcmapply(1:2, FUN = function(x) Sys.getpid())...

Getting the following error when trying to add to the domain the username and password are correct because they work on other machines. =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.04.16 09:50:06 =~=~=~=~=~=~=~=~=~=~=~= INFO: Current debug levels: all: 5 tdb: 5 printdrivers: 5 lanman: 5 smb: 5 rpc_parse: 5 rpc_srv: 5 rpc_cli: 5 passdb: 5 sam: 5 auth: 5 winbind: 5 vfs: 5

Hi, I am tracking down a problem and would like to know how I can follow a forked process with my dtrace script, or how I can trace a dynamic library. Here is the problem. I am tracing dtlogin, and specifically I am trying to determine what error libpkcs11`<routine> is returning. It turns out dtlogin forks a lot of processes, and I believe the second forked process is t...

On Tue, Jul 12, 2016 at 10:00 AM, mathias dufresne <infractory at gmail.com> wrote: > Chris, can you check into your unit file what kind of type is used? Mine use Type=forking, I had some issues with Type=notify but it's been some time so I can't remember what they were. Although one is that a "systemctl start samba" command did not return a prompt, had to Ctrl-C out.

...y really bad at explaining the problem, but here's my last attempt of an example: Consider PkgA::train() that calls mclapply(..., PkgB::estimate). Life is good. Then PkgB fixes a bug in the estimator + optimizes some the internals/native code - unfortunately, the latter is not meant to work in forked parallel processing. Author of PkgB have not idea that this change will affect PkgA negatively. When PkgB hits CRAN, the problem in PkgA might go undetected, e.g. low code coverage in package tests or for other reasons. Now CRAN distributes an unstable software stack. All code bases relying on P...

I have a VPS running C7. I ran a 'yum update' which included a kernel update. The yum update wasn't a total success because mariadb updates failed. However everything else appeared to work. However, when I rebooted the server it did not restart. I have managed to get the ISP's support desk to boot the server by selecting the previous kernel, and I now have access to my box again.

On Mon, 15 Apr 2019 at 08:44, Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 4/13/19 12:05 PM, I?aki Ucar wrote: > > On Sat, 13 Apr 2019 at 03:51, Kevin Ushey <kevinushey at gmail.com> wrote: > >> I think it's worth saying that mclapply() works as documented > > Mostly, yes. But it says nothing about fork's copy-on-write and memory >

On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux <syslinux at zytor.com> wrote: > Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115 A fork is a fork, regardless the reasons behind it (yes, I have some understanding in this case). iPXE is based off of forking further development as of a certain gPXE commit with some backporting of gPXE development to iPXE. --

...ateWidget package, which lives on Github at https://github.com/rte-antares-rpackage/manipulateWidget/. Last week I found a bug, so being a good community member, I put together a patch. Since the package lives on Github, I followed instructions to put together a "pull request": - I forked the main branch to my own Github account as <https://github.com/dmurdoch/manipulateWidget>. - I checked out my fork into RStudio. - I fixed the bug, and submitted the pull request <https://github.com/rte-antares-rpackage/manipulateWidget/pull/47>. Then I felt good about myself, and...

I am seeking a better workaround than I currently have for the problem. Using OS X 10.3.x and 10.4.x (and possibly other versions) as workstations, and Gentoo Linux (kernel 2.6.16) with Samba 3.0.22, I have the following sequence of events. The symptom is most prevalent when dealing with multi MB files: 1. Resource fork (._ file) gets locked 2. File associated with resource fork also gets

...> > > > > On Jan 10, 2020, at 10:58 AM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > > > > The RStudio GUI was just one example. AFAIK, and please correct me if > > I'm wrong, another example is where multi-threaded code is used in > > forked processing and that's sometimes unstable. Yes another, which > > might be multi-thread related or not, is > > https://stat.ethz.ch/pipermail/r-devel/2018-September/076845.html: > > > > res <- parallel::mclapply(urls, function(url) { > > download.file(url, base...

The RStudio GUI was just one example. AFAIK, and please correct me if I'm wrong, another example is where multi-threaded code is used in forked processing and that's sometimes unstable. Yes another, which might be multi-thread related or not, is https://stat.ethz.ch/pipermail/r-devel/2018-September/076845.html: res <- parallel::mclapply(urls, function(url) { download.file(url, basename(url)) }) That was reported to fail on macO...