Environment variable propagation
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 110
- Forks
- 35
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 2
Description
When using ssh/rsh to spin up servers, environment variables are propagated from the front end node.
Add, e.g., a -e flag to spindle to allow the user to specify which environment variables to propagate.
The issue first came up when testing slurm+ssh in an ubuntu environment where TMPDIR was not set. Adding TMPDIR to the front end node was not sufficient as it wasn't sent along to the servers.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating spindle's command-line option handling and the ssh/rsh server-launch path; trace how the existing environment is propagated. Done means users can select variables with an -e option and those variables reach the spawned servers, including the TMPDIR case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100