[bind10-dev] Issues on a BIND10 package of Fedora 19

[Naoki Kambe]

Hello Mukund-san,

From: Mukund Sivaraman <muks at isc.org>
Date: Thu, 16 May 2013 19:06:00 +0530
> logger_lockfile is automatically removed when b10-init shuts down. For
> it to have permissions to create logger_lockfile, the permissions on the
> directory have to allow it. During a "make install", we set mode 02770
> on the local state directory (var/bind10-devel/), but it may be that the
> package spec does not do so.

If I set a setgid bit to the directory /var/bind10, bind10 works.  And
we don't have to recreate a lockfile.

[kambe at fedora19a ~]$ sudo systemctl stop bind10.service
[kambe at fedora19a ~]$ ls -ld /var/bind10
drwxrwxr-t. 2 root named 4096 May 17 09:22 /var/bind10
[kambe at fedora19a ~]$ sudo chmod g+s /var/bind10
[kambe at fedora19a ~]$ ls -ld /var/bind10
drwxrwsr-t. 2 root named 4096 May 17 09:22 /var/bind10
[kambe at fedora19a ~]$ sudo systemctl start bind10.service
[kambe at fedora19a ~]$ ls -l /var/bind10/logger_lockfile
-rw-rw----. 1 root named 0 May 17 09:13 /var/bind10/logger_lockfile
[kambe at fedora19a ~]$ sudo systemctl status bind10.service
bind10.service - BIND10 DNS and DHCP service
   Loaded: loaded (/usr/lib/systemd/system/bind10.service; disabled)
   Active: active (running) since Fri 2013-05-17 09:22:50 JST; 17s ago
 Main PID: 11510 (b10-init)
   CGroup: name=systemd:/system/bind10.service
...

In the error message,

| FATAL [b10-init.init]: BIND10_STARTUP_ERROR error during startup:
...
| often you need to start bind10 as a super user.  Also, if you
| specify the -u option to change the user and group, the directory
| must be writable for the group, and the created lock file must be
| writable for that user.
...

we also might need to mention that to set a setgid bit to the
directory is required.

Thanks,

Naoki Kambe