Skip to content

rfc42: add continued exec response - #570

Open
chu11 wants to merge 1 commit into
flux-framework:masterfrom
chu11:rfc42_sigcont
Open

chu11 wants to merge 1 commit into
flux-framework:masterfrom
chu11:rfc42_sigcont

Conversation

@chu11

@chu11 chu11 commented Nov 6, 2026

Copy link
Copy Markdown
Member

Problem: Presently a response to indicate a subprocess has received a SIGCONT signal is not supported.

Add a new "exec continued" response to support this reporting.


This is to match work in flux-framework/flux-core#7842

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

⚠️ linkcheck failed with status code 2

@garlick garlick left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think an exec continued response will be needed for attach too.

Also, should we mention that a STOP immediately followed by a CONT and vice versa may be suppressed, as in posix SIGCONT handling (with reference)?

@chu11

chu11 commented Nov 6, 2026 •

Copy link
Copy Markdown
Member Author

Also, should we mention that a STOP immediately followed by a CONT and vice versa may be suppressed, as in posix SIGCONT handling (with reference)?

I did think about that, but figured it was an implementation choice and not something the protocol should define?

Problem: Presently a response to indicate a subprocess has received
a SIGCONT signal is not supported.

Add a new "exec continued" response to support this reporting.
@chu11

chu11 commented Nov 8, 2026

Copy link
Copy Markdown
Member Author

I think an exec continued response will be needed for attach too.

re-pushed, adding the attach part too.

@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown

⚠️ linkcheck failed with status code 2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants