Hi Gennadiy,
On 20 July 2021 at 10:25, Gennadiy Starostin wrote:
| Thank you for your feedback. There was a misconfigured redirection
| indeed. It should work well now.
Fabulous, thanks as always.
| The top page does say "If you experience any problems or need help you
| can submit a suppor
We are working on rearranging some of our header files with the goal
of making the installed headers correspond more closely to the C API
available to packages. Packages that only use entry points and
definitions that are part of the API as specified in Chapter 6 of
Writing R Extensions should not
Dear Dirk,
Thank you for your feedback. There was a misconfigured redirection
indeed. It should work well now.
The top page does say "If you experience any problems or need help you
can submit a support request to the R-Forge team or write an email to
r-fo...@r-project.org.
Thanks... and en
Thanks for your explanation. This makes a lot of sense! SIGINT
handling is a blind spot to me, this introduction looks perfect!
Best,
Jiefei
On Tue, Jul 20, 2021 at 4:31 PM Tomas Kalibera wrote:
>
> Hi Jiefei,
>
> when you run the cluster "automatically" in your terminal and pres
> Ctrl-C in Uni
Hi Jiefei,
when you run the cluster "automatically" in your terminal and pres
Ctrl-C in Unix, both the master and the worker processes get the SIGINT
signal, because they belong to the same foreground process group. So you
are directly interrupting also the worker process.
When you run the c
Hi all,
I just notice this interesting problem a few days before, but I cannot
find an answer for it. Say if you have a long-running job in a cluster
made by the parallel package and you decide to stop the execution by
pressing ctr + c in the terminal or the stop button in Rstudio for
some reason.
