Actions
Bug #8195
closedBIND packages launches two instances of /usr/local/sbin/named on boot
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
BIND
Target version:
-
Start date:
12/12/2017
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
2.4.2-RELEASE with BIND 9.11_9 on SG-4860
With the BIND package installed and enabled, I see two identical "/usr/local/sbin/named -c /etc/namedb/named.conf -u bind -t /cf/named/" processes running after a reboot. This does not appear to affect functionality (presumably one simply fails to bind to any interfaces), but nevertheless seems like behavior that should be fixed.
Actions