SIG_MSG_END #2

New issue

Open

opened 2026-03-04 06:31:31 +00:00 by jaynuine · 1 comment

jaynuine commented

2026-03-04 06:31:31 +00:00

Owner

No description provided.

jaynuine added this to the >9000 milestone

2026-03-04 06:32:15 +00:00

jaynuine added this to the todo project

2026-03-04 06:32:26 +00:00

jaynuine changed title from ~~reserve signal to communicate server shutdown~~ to SIG_MSG_END

2026-03-26 04:45:07 +00:00

jaynuine commented

2026-03-26 04:52:55 +00:00

Author

Owner

server shutdown is already able to be tested by checking the return value of kill-ing the server to assert that pid being assigned

i guess were the pid reused we could have issues ? edge case but possible

maybe sending SIG_MSG_END outside of any real time communication could serve as the shutdown signal ?
like if no SIG_ACKNOWLEDGE is being awaited and a SIG_MSG_END is received that could serve as a SIG_TERMINATE

besides "terminate" may be confused for an outgoing instruction telling the clients to terminate which is not what this is

server shutdown is already able to be tested by checking the return value of kill-ing the server to assert that pid being assigned i guess were the pid reused we could have issues ? edge case but possible maybe sending SIG_MSG_END outside of any real time communication could serve as the shutdown signal ? like if no SIG_ACKNOWLEDGE is being awaited and a SIG_MSG_END is received that could serve as a SIG_TERMINATE besides "terminate" may be confused for an outgoing instruction telling the clients to terminate which is not what this is

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jaynuine/minitalk#2

No description provided.

Rows
Columns