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

flux-start: only a single local session is supported #13

Closed
grondo opened this issue Sep 30, 2014 · 2 comments
Closed

flux-start: only a single local session is supported #13

grondo opened this issue Sep 30, 2014 · 2 comments
Labels

Comments

@grondo
Copy link
Contributor

grondo commented Sep 30, 2014

For running tests in parallel it will be nice if flux-start allowed multiple local comms sessions
to start at the same time. Currently I get

$ ./flux start --size=2
cmbd: cmbd is already running in /var/tmp/grondo/flux-0-1, pid 84630
cmbd: cmbd is already running in /var/tmp/grondo/flux-0-0, pid 84629
flux-start: 0 (pid 84679) exited with rc=1
flux-start: 1 (pid 84680) exited with rc=1

I'm guessing this will probably be a trivial fix, but I want to note it here so we don't lose track of the feature request.

@garlick
Copy link
Member

garlick commented Oct 1, 2014

FLUX_TMPDIR is set to $FLUX_TMPDIR (or $TMPDIR, or /tmp) /flux-<session_id>-<rank>.
For an srun launch, <session_id> is set to the PMI "appnum" which slurm sets to job id.
For a direct launch, <session_id> is set to 0. What about changing that case to a uuid (provided by flux-start to all its children on the command line?)

@garlick garlick added the bug label Oct 16, 2014
garlick added a commit to garlick/flux-core that referenced this issue Oct 17, 2014
This applies to local session only:  use pid of flux-start for
session id instead of letting the default of '0' be used.
This allows concurrent local sessions.  Fixes issue flux-framework#13.
@grondo
Copy link
Contributor Author

grondo commented Oct 17, 2014

Hm, commit 878361e didn't auto-close this issue. Perhaps the "Fixes Issue #..." needs to be on its own line? I also just learned that it is possible to close an issue from a pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants