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

switch from no-daemon to keep-in-foreground #11

Open

captn3m0 opened this issue Jan 23, 2019 · 1 comment

captn3m0 commented Jan 23, 2019

From dnsmasq docs:

-d, --no-daemon

Debug mode: don't fork to the background, don't write a pid file, don't change user id, generate a complete cache dump on receipt on SIGUSR1, log to stderr as well as syslog, don't fork new processes to handle TCP queries. Note that this option is for use in debugging only, to stop dnsmasq daemonising in production, use --keep-in-foreground.

I haven't worked that much with dnsmasq, so if --no-daemon is more correct for Docker usage, it would be nice to know why.

The text was updated successfully, but these errors were encountered:

Owner

jpillora commented Jan 24, 2019

http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html

-k, --keep-in-foreground
Do not go into the background at startup but otherwise run as normal. This is intended for use when dnsmasq is run under daemontools or launchd.

You are correct, we should be using --keep-in-foreground

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment