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

Does `do-daemonize:no` make sense in unbound? #123

Open

vonHabsi opened this issue Jan 2, 2025 · 0 comments

vonHabsi commented Jan 2, 2025 •

edited

Loading

I installed the Pihole-Unbound combination and I found Unbound to be very slow.

Looking through the configuration I saw do-daemonize: no, which suggests that a new call or instance needs to be launched to handle a request.

After changing it to do-daemonize: yes performance appears to have improved.

Does do-daemonize: no make sense for a tool that needs to respond quickly?

According to the docs do-daemonize: no is used when unbound is run as a systemd service.

Does this docker version run as a systemd service?

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

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