HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND

Jan Lentfer Jan.Lentfer at web.de
Mon Apr 12 13:09:15 PDT 2010


Jeremy C. Reed schrieb:
On Mon, 12 Apr 2010, Jan Lentfer wrote:

  
Copy or link the rc script to /etc/rc.d/
# ln -s /usr/pkg/share/examples/rc.d/named9 /etc/rc.d/
      
Don't link, copy. It seems a link is not working during boot.
    
Probably /usr/pkg not mounted yet?

  
Possibly. But /usr/pkg is just a pfs null mount. Shouldn' t that get 
mounted before /etc/rc.d/named9 gets run?


# cp /usr/pkg/share/examples/rc.d/named9 /etc/rc.d/
    
pkgsrc packages provide mechanism to do this automatically.
PKG_RCD_SCRIPTS=yes in the environment when doing a pkg_add of bind9.
(Also PKG_CONFIG=yes but that is the default.)
Same if installing from pkgsrc.
  
Wasn't aware of that. Thanks for the pointer.
Stop your base-BIND
# /etc/rc.d/named stop
      
Somehow on reboot the rc-script didn't pick up the right binary. So I also
added:
    
edit /etc/rc.conf  remove named_enable="YES", then add

named9_enable="YES"
named_chrootdir="/etc/namedb"
      
So the plan is to remove that from etc/defaults/rc.conf?

  
Good point again :-). Havn't thought about it so far but it makes sense 
to remove it from defaults/rc.conf if it is not part of base anymore.


named_flags="-c named.conf"
      
Why?
  
If I don't set it named refuses to start with:
Apr 12 21:58:49 epia named[49440]: none:0: open: /etc/named.conf: file 
not found


named_program="/usr/pkg/sbin/named"
  

The script already sets "command". Maybe you have a conflict with 
named_program in etc/defaults/rc.conf?

  
I was wondering about that one, too. Command is set in named9, right. 
But if you don't set it like this, you will get
/etc/rc.d/named9: INFO: run_rc_command: cannot run (/usr/sbin/named).
It picks up named_program from default/rc.conf still. This will not be 
necessary as soon as named_program is removed from defaults/rc.conf, I 
just tested this.

The BIND packaged from pkgsrc is running with user named instead of bind,
so..
# chown -R named /etc/namedb
      
But that doesn't help if you need to temporarily revert to other named. 
Set alternative using named_flags="-u bind" or set 
BIND_USER and BIND_GROUP as appropriate in the mk.conf files when 
building packages.

  
Many roads will get you to the finish :-). If you pkg_radd will 
BIND_USER and BIND_GROUP in mk.conf still be taken into account? If you 
have to switch back you have to issue a "chown -R bind /etc/namedb" with 
my approach. I'd think the effort is about the same.

Thanks for the input!

Jan





More information about the Users mailing list