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.

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

Fix exit(2) on SIGHUP before fully initialized. #378

Merged
merged 1 commit into from
Sep 30, 2021

Conversation

JoelLinn
Copy link
Contributor

docker-gen uses SIGHUP to trigger regeneration.
However, when SIGHUP is fired before docker-gen is fully initialized (and the signal handler was installed), the process will just exit(2).
This fix ignores SIGHUP until the signal handler is installed.

Fixes #244

@JoelLinn
Copy link
Contributor Author

#244 (comment)

@buchdag
Copy link
Member

buchdag commented Sep 30, 2021

HI @JoelLinn, thanks for catching and fixing this one. Have you been able to test the fix in production ?

Edit: looking at the issue seems like yes, you and others did.

@JoelLinn
Copy link
Contributor Author

I have deployed this fix (as my custom build on-top the master tip of that time) over a year ago on about 40 servers and didn’t have any (re-)generation problems since then.

It seems to be the root cause for the issue #244 (although the issue title is pretty generic so there might be all sorts of causes for a phenomenon like it)

I’m happy this project is maintained again ☺️

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.

Restart unless stopped not working
2 participants