Skip to content
This repository was archived by the owner on Feb 5, 2025. It is now read-only.

Don't remove socket when exiting forked process#130

Open
vtrlx wants to merge 1 commit intodeadpixi:masterfrom
vtrlx:vtrlx
Open

Don't remove socket when exiting forked process#130
vtrlx wants to merge 1 commit intodeadpixi:masterfrom
vtrlx:vtrlx

Conversation

@vtrlx
Copy link

@vtrlx vtrlx commented Apr 29, 2024

Previously, using any command that forked sam would run the odd risk of causing sam's control socket to exit. This seems to be a consequence of using atexit() to schedule removal of the control socket from the file system.

This commit adds a global boolean named forked, which is set to true in child process after they are forked. The exit handlers removesocket() and rmsocket() are changed such that they don't remove the control sockets if the forked boolean is set to true.

Sam's control socket should only get removed once the main instance exits.

Fixes #75

Previously, using any command that forked sam would run the odd risk of causing sam's control socket to exit. This seems to be a consequence of using atexit() to schedule removal of the control socket from the file system.

This commit adds a global boolean named forked, which is set to true in child process after they are forked. The exit handlers removesocket() and rmsocket() are changed such that they don't remove the control sockets if the forked boolean is set to true.

Sam's control socket should only get removed once the main instance exits.

Fixes deadpixi#75
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Connection to command socket is lost during run of samterm

1 participant