Jim Garlick

This is probably going to be needed sooner rather than later so attaching to next release milestone.

Dropping from the next release milestone since this is now tracked in a feature tracker, and we likely won't need it for a few months given current rollout plans which...

For completeness the failing flux is flux-core 0.38.0 ``` [garlick@lassen709:~]$ which flux /usr/bin/flux [garlick@lassen709:~]$ flux version commands: 0.38.0 libflux-core: 0.38.0 build-options: +hwloc==1.11.0+zmq==4.1.5 ```

Possibly it's because it wasn't configured `--with-pmix-bootstrap`, whereas ``` [garlick@lassen709:flux-core]$ /usr/global/tools/flux/blueos_3_ppc64le_ib/flux-c0.29.0-s0.18.0/bin/flux version commands: 0.29.0 libflux-core: 0.29.0 build-options: +pmix-bootstrap==3.1.4+hwloc==1.11.6+zmq==4.1.5 ```

an obscure one to be sure. We'll want to be sure to add that to the rpm spec file, conditional on the architecture.

Just a couple of notes since I've not really been on that system much. There are three rpm packaged versions of pmix, all side installed under /usr/pmix with no pkgconfig...

Is this supposed to work? It just hangs for me ``` $ lalloc 2 [snip] Job is submitted to default queue . $ lrun -n2 hostname ```

> I wonder if this also explains the problem with `-Srundir=/path/to/shared/fs` on that system, since each broker thinks it is rank 0, each one tries to create the same socket...

Meh I'd say don't let guests make symlinks if it simplifies our lives. The main use case is linking from primary namespace to a "live" job namespace.

Wait, I'm not sure a loopy or dangling symlink is a problem. It's definitely not a problem for `flux-dump` and `flux-restore` since they never follow them. In regular file systems,...