diff options
| author | dougb <dougb@FreeBSD.org> | 2005-04-24 01:51:22 +0000 |
|---|---|---|
| committer | dougb <dougb@FreeBSD.org> | 2005-04-24 01:51:22 +0000 |
| commit | 37f3e68064dc086c20a3745611a2a96b44760e8e (patch) | |
| tree | da2c185c2a6fe0ff80a482dac463f425ab9e3eb1 /etc | |
| parent | 6149b9f287815806eafa12f8ff1b310ea904e25b (diff) | |
| download | FreeBSD-src-37f3e68064dc086c20a3745611a2a96b44760e8e.zip FreeBSD-src-37f3e68064dc086c20a3745611a2a96b44760e8e.tar.gz | |
Add -h to the ln command to make the -f flag actually do something.
Without this flag, if the symlink existed already a new symlink would
be created in the source directory. While harmless if the two symlinks
were the same, it nonetheless caused pointless confusion.
The pathological case is that when there is an existing /etc/namedb
symlink, but named_chrootdir in rc.conf pointed to a different
directory, it was the symlink in /var/named that was getting
updated, not the one in /etc. This led to some difficult to diagnose
problems for users.
Diffstat (limited to 'etc')
| -rwxr-xr-x | etc/rc.d/named | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/etc/rc.d/named b/etc/rc.d/named index 660caed..039820d 100755 --- a/etc/rc.d/named +++ b/etc/rc.d/named @@ -52,7 +52,7 @@ chroot_autoupdate() fi else # Make sure it points to the right place. - ln -sf ${named_chrootdir}/etc/namedb /etc/namedb + ln -shf ${named_chrootdir}/etc/namedb /etc/namedb fi |
