Mailinglist Archive: opensuse (1698 mails)

[lynn <lynn@xxxxxxxxxxxx>]

Hi everyone
12.1
BIND 9.8.1-P1
named running without chroot

Restarting bind with the init script produces:

Starting name server BIND ln: failed to create
symbolic link `/var/run/named/named': File exists

hh3:/var/run/named # ls -la
total 8
drwxr-xr-x  2 named named 100 Dec 20 20:30 .
drwxr-xr-x 23 root  root  740 Dec 20 19:56 ..
lrwxrwxrwx  1 root  root   14 Dec 20 20:10 named -> /var/run/named
-rw-r--r--  1 named named   5 Dec 20 20:30 named.pid
-rw-------  1 named named 102 Dec 20 20:30 session.key

Stop bind and we get:
hh3:/var/run/named # ls -la
total 0
drwxr-xr-x  2 named named  60 Dec 20 20:31 .
drwxr-xr-x 23 root  root  740 Dec 20 19:56 ..
lrwxrwxrwx  1 root  root   14 Dec 20 20:10 named -> /var/run/named

The workaround is not to use /etc/init.d/named:

    killall -9 named
    chkconfig named off
    rm -r /var/run/named
    mkdir /var/run/named
    chown named:root /var/run/named
    named -u named

1. Why is the link, named -> /var/run/named created?
2. If the link needs to be created upon starting and deleted upon 
ending, then why does root create it?

Need confirmation that this is not a bug.
Thanks for your patience.
L x






--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx