search for: forks

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

Hello Samba Group Today installing the Samba Version 4.11.7-Debian pkg from Louis, Thanks Louis !! The Server will running but watching on the service i have DNS Problmes. Please can give me any update here : what are runing wrong. -- samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled) Active:

Henrik, 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

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

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 3:10 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > On Fri, Jan 10, 2020 at 7:23 PM Simon Urbanek > <simon.urbanek at r-project.org> wrote: >> >> Henrik, >> >> 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. > > I

...() should have an option to not print anything - it just makes no sense. If you have code that is fork-incompatilble, you clearly cannot use it in mcparallel - that's why there is a very explicit warning in the documentation. As I said, if you have some software that embeds R and has issue with forks, then that software should be use pthread_atfork() to control the behavior. Cheers, Simon > On Jan 10, 2020, at 3:34 PM, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: > > On Fri, Jan 10, 2020 at 11:23 AM Simon Urbanek > <simon.urbanek at r-project.org> wrote:...

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

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

...acking 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 the one that winds up having a failing call to libpkcs11`<routine>. Of course, when I start dtrace, the forked process is not yet created, so I can not specify that. Also, it appears I can not just trace on libpkcs11`<routine...

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.

...s. Usage of forking will come and go in that software stack completely out of control to the user. They could be in control if there was an option to disable it. I don't think the analogue to print() is relevant here. > As I said, if you have some software that embeds R and has issue with forks, then that software should be use pthread_atfork() to control the behavior. If I understand this correctly, this only applies to discussions such as RStudio and similar. It is not a relevant solution to ordinary users of R, correct? I'm not sure if you're playing devils advocate here, or...

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

Lately I've been doing some work with the manipulateWidget 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

...with NFS. On the Mac side, we're evaluating "DAVE" (an SMB client program to replace OSX's native SMB implementation). It's meeting with some resistance from my Mac users, as the UI is not as convenient as the builtin interface and has some problems with locating resource forks, even as it avoids removing hours or days worth of productivity. Our other options are to go to AFP via netatalk (which may not resolve the problem), to live with the problem, or to purchase a Mac X server and move our Macs off Samba. None of these solutions look really attractive, as they...

On Fri, Jan 10, 2020 at 11:23 AM Simon Urbanek <simon.urbanek at r-project.org> wrote: > > Henrik, > > 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. Thanks for ruling that example out. > That's exactly why I was proposing a more general solution where you can simply define

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,