search for: fork

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 proces...

...8) man:samba(7) man:smb.conf(5) Main PID: 4339 (samba) Status: "smbd: ready to serve connections..." Tasks: 61 (limit: 4915) Memory: 190.5M CGroup: /system.slice/samba-ad-dc.service +-4339 samba: root process +-4340 samba: tfork waiter process +-4341 samba: task[s3fs] pre-fork master +-4342 samba: tfork waiter process +-4343 samba: task[rpc] pre-fork master +-4344 samba: tfork waiter process +-4345 samba: tfork waiter process +-4346 /usr/sbin/smbd -D -...

...the example from the post works just fine in CRAN R for me - the post was about homebrew build so it's conceivably a bug in their libraries. That's exactly why I was proposing a more general solution where you can simply define a function in user-space that will issue a warning or stop on fork, it doesn't have to be part of core R, there are other packages that use fork() as well, so what I proposed is much safer than hacking the parallel package. Cheers, Simon > On Jan 10, 2020, at 10:58 AM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > > The RStudio...

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::makeCluste...

If I understand the thread correctly this is an RStudio issue and I would suggest that the developers consider using pthread_atfork() so RStudio can handle forking as they deem fit (bail out with an error or make RStudio work). Note that in principle the functionality requested here can be easily implemented in a package so R doesn?t need to be modified. Cheers, Simon Sent from my iPhone >> On Jan 10, 2020, at 04:34,...

...in their libraries. > > I think it works now, because Apple switched to a different SSL > library for libcurl. It usually crashes or fails on older macOS > versions, with the CRAN build of R as well. > > It is not a bug in any library, it is just that macOS does not support > fork() without an immediate exec(). > > In general, any code that calls the macOS system libraries might > crash. (Except for CoreFoundation, which seems to be fine, but AFAIR > there is no guarantee for that, either.) > That is not true, either. macOS itself is fork-safe (it is POSIX-...

Henrik, the whole point and only purpose of mc* functions is to fork. That's what the multicore package was about, so if you don't want to fork, don't use mc* functions - they don't have any other purpose. I really fail to see the point - if you use mc* functions you're very explicitly asking for forking - so your argument is like saying that pri...

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 be...

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(...

...d doing parameter gpfs:sharemodes = no doing parameter force unknown acl user = yes doing parameter bind interfaces only = yes doing parameter interfaces = vlan199 doing parameter ctdbd socket = /usr/local/var/run/ctdb/ctdbd.socket doing parameter passdb backend = tdbsam doing parameter workgroup = FORK doing parameter realm = fork.viasat.dom doing parameter clustering = yes doing parameter idmap config *:backend = tdb2 doing parameter dedicated keytab file = /etc/krb5.keytab doing parameter kerberos method = secrets and keytab doing parameter security = ads doing parameter winbind enum users = ye...

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...

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.

On Fri, Jan 10, 2020 at 7:23 PM Simon Urbanek <simon.urbanek at r-project.org> wrote: > > Henrik, > > the whole point and only purpose of mc* functions is to fork. That's what the multicore package was about, so if you don't want to fork, don't use mc* functions - they don't have any other purpose. But, with that same argument I'm surprised we have fake implementations of the mc***() functions for MS Windows. > I really fail to see t...

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.

...libera 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 > > overcommitment, and that this means that it may work nicely or fail > > spectacularly depending on whether, e.g., you operate on a long > > vector. > > R cannot possibly replicate documentation of the underlying operating > systems. It c...

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. -- -Gene

...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, a...

...rkaround 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 locked. 3. File gets unlocked 4. Resource fork never gets unlocked. Because the resource fork never gets unlocked, this causes problems with migration of data off the Mac to the server and occasionally results in a file bei...

...in CRAN R for me - the post was about homebrew build so it's conceivably a bug in their libraries. Thanks for ruling that example out. > That's exactly why I was proposing a more general solution where you can simply define a function in user-space that will issue a warning or stop on fork, it doesn't have to be part of core R, there are other packages that use fork() as well, so what I proposed is much safer than hacking the parallel package. I think this is worth pursuing and will help improve and stabilize things. But issuing a warning or stop on fork will not allow end user...

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 ma...