bind9: logging to file doesn't work cause bind starts with -g option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Docker Images |
Fix Released
|
Low
|
Athos Ribeiro |
Bug Description
Hi,
I use ubuntu/
Here is my logging conf :
+------
| # cat /etc/bind/
| [...]
| logging {
| channel query {
| file "/var/log/
| severity info;
| print-time yes;
| };
| category queries { query; };
| };
| [...]
+------
File /var/log/
Bind starts with -g option and I think it causes the issue :
+------
| # ps ax|grep named
| 1 ? Ssl 0:00 /usr/sbin/named -u bind -g
+------
I don't understand from where the -g option is set :
+------
| # cat /etc/default/named
| #
| # run resolvconf?
| RESOLVCONF=no
|
| # startup options for the server
| OPTIONS="-u bind"
+------
Can someone help me ?
Thanks
Related branches
- Sergio Durigan Junior: Approve
- Bryce Harrington: Pending requested
- Canonical Server Reporter: Pending requested
-
Diff: 31 lines (+11/-2)1 file modifieddocker-entrypoint.sh (+11/-2)
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Hello,
please check the entrypoint code at /git.launchpad. net/~ubuntu- docker- images/ ubuntu- docker- images/ +git/bind9/ tree/docker- entrypoint. sh?h=9. 18-22.04 bin/entry- point.sh in your image) this is where the -g option comes from.
https:/
(or at /usr/local/
From that file, you will also notice that you should be able to either pass additional params to bind through CMD, or to even override the whole startup command by starting CMD with "named".
The reason it starts with the -g option is to make it simpler to run it in environments such as kubernetes.