Use random temporary file name for rserver secure cookie key #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the batchspawner, we can have several rserver session started on the same cluster node. However, rserver is by default using the same path
/tmp/rstudio-server/secure-cookie-key
to store secure cookie key. As a result the cookie key file is locked and owned by the first user starting a RStudio session on a given node.To avoid this, we need to define a distinct temporary file for rserver secure cookie key for each rserver instance.