Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is rserve interrupt working for Windows? #52

Closed
maxyeg opened this issue Dec 11, 2015 · 1 comment
Closed

Is rserve interrupt working for Windows? #52

maxyeg opened this issue Dec 11, 2015 · 1 comment

Comments

@maxyeg
Copy link

maxyeg commented Dec 11, 2015

Hi!
I'd like to confirm if rserve can be interrupted(not killed) in windows properly.
I've searched your repository for SIGINT occurrences and see some expressions like #ifdef unix.
I'm not sure but maybe rserve won't handle SIGINT in windows?

I start rserve by run.Rserve(...) and it will be interrupted in unix if needed using: kill -SIGINT pid.

@s-u
Copy link
Owner

s-u commented Jan 24, 2016

Windows doesn't support unix signals. I'm not aware of a corresponding facility on Windows. Their idea of "signals" is intra-process only. There are ways in which you can enter R on idle (e.g. by running a parallel thread with its own window context and issuing a Win32 message - see the background package), but have not tried to use it for this purpose. Given how of little use and limited is Windows with R computing, Rserve doesn't try to implement anything Windows-specific in this regard.

@s-u s-u closed this as completed Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants