Installing bind9 as per HACKING.txt leaves a running bind daemon on developer's machines
Bug #1026857 reported by
Julian Edwards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Julian Edwards | ||
bind9 (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
MAAS brings up short-lived instances of named in its test suite,
and when running in "development" mode. It requires that bind9 is
installed, but does not use the system instance of named. It
would be useful to have an option to disable start of bind9. This
may also be useful if running an alternative nameserver on the
machine.
Related branches
lp://staging/~julian-edwards/maas/bind-hacking
- Raphaël Badin (community): Approve
-
Diff: 15 lines (+5/-0)1 file modifiedHACKING.txt (+5/-0)
Changed in bind9 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in maas: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
status: | Triaged → Fix Released |
To post a comment you must log in.
One way to stop it is to put
exit 1
at the top of /etc/default/bind9