Olaf Faaland

> As described by @kathrynmohror in https://github.com/flux-framework/flux-core/issues/2040: > > From what Dong said, you are discussing the case where something like SCR would need to hold on to allocation resources...

> Olaf Faaland wants to make use of prologue and epilogue scripts on Elmerfudd to: > > > (1) Run a script to clean up /dev/shm after a job, so...

> Unfortunately a job-shell plugin won't work for any of these use cases since it runs as the user of the job, not a privileged process. > > We do...

Or perhaps this? enum flux_process_scope { init, job }; enum flux_process_scope flux_get_process_scope (void); Then the consumer can use the returned value directly in a conditional expression, and avoid bugs like...

FWIW, If the documentation includes one example command or situation for each state, it might bo a long way towards helping users understand what the states are and how to...

Currently a node failure is fatal to the allocation, although there is a few-second period after the downed node is drained and before the allocation is lost: ``` [faaland1@fluke6 ~]...

@adammoody and @kathrynmohror FYI

Thanks @garlick. > we'll want a way to increase the TBON fanout ... Losing a router node currently causes loss of its subtree Are there plans to make the tree...

@trws @garlick I'm following up on @kathrynmohror 's conversation with Tom. If I understand correctly, fully satisfying this use case requires multiple changes to flux. Is that correct? And is...

Cool, thanks Jim.