Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't remove socket when exiting forked process #130

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Don't remove socket when exiting forked process #130

wants to merge 1 commit into from

Commits on Apr 29, 2024

  1. Don't remove socket when exiting forked process 

    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
    @vtrlx
    vtrlx committed Apr 29, 2024
    Configuration menu
    Copy the full SHA
    573f103 View commit details
    Browse the repository at this point in the history