-
Notifications
You must be signed in to change notification settings - Fork 65
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
Time limited Rserve session #199
Comments
Once the connection is established, you have full control over what the session will do, so you can terminate the session whenever you feel like it which will close the connection on the client side. There are many way you can do this - if you really want to terminate the session regardless, you can use a watchdog child process that will wait until the time is up and then kill the session:
The For example can put it in
You could improve the above by checking on the session more often (so the watchdog can quit early) and you could add warnings to the user etc. You could also be less aggressive and only interrupt etc. |
Have checked it....works smoothly. For linux server I guess (not windows), but that is what I needed. Thanks a lot for this ! |
I had a follow-up question regarding your suggestion about "watchdog can quit early". If the user exits early using say RS.close(c), the master is exiting. It should ideally kill any running child processes such as watchdog by sending some signal. It seems this is not the case for RS.close(c) ? Is there any way to achieve this from the master, or checking intermittently from the child is the only possibility? |
I would like to terminate a client's Rserve session if a certain amount of time expires or based on some other criteria. Alternatively, require the client to log in/authenticate again. Is there any way to do this in Rserve ?
The text was updated successfully, but these errors were encountered: