[Bug 201423] dns/bind910: when using base OpenSSL bind should not try to umount

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201423

            Bug ID: 201423
           Summary: dns/bind910: when using base OpenSSL bind should not
                    try to umount
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: mat at FreeBSD.org
          Reporter: girgen at FreeBSD.org
          Assignee: mat at FreeBSD.org
             Flags: maintainer-feedback?(mat at FreeBSD.org)

Quick question. I get this warning every time I shut down bind910:

Stopping named.
umount: /var/namedb/usr/local/lib/engines: statfs: No such file or directory
umount: /var/namedb/usr/local/lib/engines: unknown file system


I don't use ports' OpenSSL. When mounting the ports' OpenSSL engines directory,
the rc.d/named script checks for -d ${_openssl_engines}. Shouldn't that happen
also when unmounting? Something like this:

Index: files/named.in
===================================================================
--- files/named.in    (revision 391551)
+++ files/named.in    (working copy)
@@ -231,7 +231,7 @@

named_poststop()
{
-    if [ -n "${named_chrootdir}" -a -c ${named_chrootdir}/dev/null ]; then
+    if [ -d ${_openssl_engines} -a -n "${named_chrootdir}" -a -c
${named_chrootdir}/dev/null ]; then
        # unmount OpenSSL engines, if they were not mounted but only
        # copied, do nothing.
        if [ `${SYSCTL_N} security.jail.jailed` -eq 0 -o `${SYSCTL_N}
security.jail.mount_allowed` -eq 1 ]; then



Best regards,
Palle

-- 
You are receiving this mail because:
You are the assignee for the bug.