Bug 374497 – will not start named in default ranlevel.

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description rosomaha256 2011-07-08 21:43:34 UTC]

will not start named in default ranlevel. 
But after logging in "named" successfully launched.

rc_update show

named |      default
net.eth0 |      default
net.eth1 |      default
net.eth2 |      default



Reproducible: Always

[Comment 1 Myckel Habets 2011-07-09 07:50:09 UTC]

Please don't add stabilization teams if you don't know what we do. x86 leaving.

[Comment 2 Pacho Ramos 2011-07-10 18:16:14 UTC]

I don't understand what do you mean :(

I guess "named" is not started at boot time? What is "named"? What package does provide it?

[Comment 3 rosomaha256 2011-07-10 18:38:04 UTC]

The problem has been resolved.

* You can edit /etc/conf.d/named to customize named settings
 *
 * If you'd like to run bind in a chroot AND this is a new
 * install OR your bind doesn't already run in a chroot:
 * 1) Uncomment and set the CHROOT variable in /etc/conf.d/named.
 * 2) Run `emerge --config '=net-dns/bind-9.7.3_p3'`
 *
 *
 * NOTE: /var/bind/named.ca has been renamed to /var/bind/named.cache
 * you may need to fix your named.conf!
 *
 * NOTE: If you upgrade from <net-dns/bind-9.4.3_p5-r1, you may encounter permission problems
 * To fix the permissions do:
 * chown root:named /{etc,var}/bind /var/{run,log}/named /var/bind/{sec,pri,dyn}
 * chown root:named /var/bind/named.cache /var/bind/pri/{127,localhost}.zone /etc/bind/{bind.keys,named.conf}
 * chmod 0640 /var/bind/named.cache /var/bind/pri/{127,localhost}.zone /etc/bind/{bind.keys,named.conf}
 * chmod 0750 /etc/bind /var/bind/pri
 * chmod 0770 /var/{run,log}/named /var/bind/{,sec,dyn}

[Comment 4 Mike Gilbert 2011-07-11 00:40:02 UTC]

Resolving per comment 3.