-
Notifications
You must be signed in to change notification settings - Fork 49
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
libsubprocess: pass flags to remote subprocess #5968
Comments
related to this
we should probably rename "flags" here, as these are rexec specific flags that are internal to the implementation, they aren't the subprocess flags from the API. Unfortunately the
so to maintain backwards compatibility we wouldn't want to rename the key in the RPC if we pass along subprocess flags in some way. |
For background the protocol was simplified in #5004 and that is when the flags were added as a replacement for three explicit booleans that told whether some of the callbacks had been registered. See also RFC 42. (The current flags are a little bit strange and might need an audit - I was trying not to change too much) The point of switching to a flags integer from the booleans was to make it easier to add more possibly server dependent flags. So we could add that one you mentioned if there were a need. I don't think so at the moment though. |
It appears that subprocess flags cannot be passed to remote sub processes.
Originally only the flags
FLUX_SUBPROCESS_FLAGS_STDIO_FALLTHROUGH
andFLUX_SUBPROCESS_FLAGS_SETPGRP
were supported. The former flag has no purpose with remote subprocesses and it appears the latter is hard coded for the server.B/c of this, I'm guessing passing flags along didn't matter much, so it wasn't supported or was just outright missed.
With the addition of the
FLUX_SUBPROCESS_FLAGS_FORK_EXEC
flag (forcefork()
even ifposix_spawn()
is available), this is something we may want to pass along some day. As well as future flags.This doesn't appear to be a problem at the moment, but its something to eventually support.
The text was updated successfully, but these errors were encountered: