Mark Grondona

I could be misreading the code, but another potential issue is that it appears that if the broker gets a termination signal while running cleanup tasks or rc3, then those...

Also, another related thought: Currently when the broker gets SIGTERM it terminates the initial program, which seems reasonable. However, a case where the initial program is a batch script, and...

As a stopgap we can have the `feasibility` plugin read the defaults from configuration and send the amended jobspec to the scheduler feasibility service, with a note that the `feasibility`...

Another idea might be to amend the `job-manager.submit` request to take an optional array of jobspec updates, which would then be emitted to the eventlog by the job-manager upon receipt....

> rc scripts do not load none by default now You are probably already on it, but just in case: don't forget to update PR description if it no longer...

What is the use case for user prolog/epilog? (i.e. is there a better way to do what the user's need?)

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 have support in...

@ofaaland @jameshcorbett - I moved the discussion over to #2205 since these use cases require full prolog/epilog support and this issue is about a "user prolog/epilog"

We could define that queue constraints are combined with any user specified constraints via the `and` operator. Fluxion does not currently support `and`, but if we only use `properties` in...

> Maybe we could have flux top watch for certain kinds of activity in the job manager journal instead? Is the journal accessible by guests? I thought you had an...