-
Notifications
You must be signed in to change notification settings - Fork 324
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
Enable building of foreground default
version
#50
Comments
While it's true wrt docker-based environments, that argument does not hold up to systemd - it happily accepts Type=forking to look after forking software. |
The program is called unitd which means "unit daemon". |
Adding a compile time option only complicates things. Most users will never compile Unit, they will install it from packages. Currently, the behaviour is straightforward: daemonized by default and an option to avoid daemonization. If we introduce the compile time option, users won't know the default. |
@VBart I agree that compile-time flag which I initially proposed would introduce mixup. But as I understood from projects roadmap, you are aiming to bring Nginx Unit into container world as a first-class citizen, for me it just makes sense that applications would start in foreground unless specifically instructed not to do so. For example, with a But @igorsysoev has a point too. Which operating systems do have that utility? I searched Debian jessie|stretch|buster and CentOS7 for binary matching that name, yet I could not find any. |
foreground default
version
I meant that "unit" name is reserved for our future control utility. |
Oh, thanks for the clarification. But I see the problem with naming here. I guess I will just have to accept that |
This closes PR nginx#50 on GitHub.
Please make a compile-time option for "--no-daemon" as a default state.
In other words:
rt->daemon = NXT_DAEMON
.Docker and Systemd environments prefer master pid to stay alive and non-forking.
The text was updated successfully, but these errors were encountered: