Bug 201423
| Summary: | dns/bind910: when using base OpenSSL bind should not try to umount | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Palle Girgensohn <girgen> |
| Component: | Individual Port(s) | Assignee: | Mathieu Arnold <mat> |
| Status: | Closed FIXED | ||
| Severity: | Affects Many People | Flags: | bugzilla:
maintainer-feedback?
(mat) |
| Priority: | --- | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
A commit references this bug: Author: mat Date: Mon Aug 31 10:06:28 UTC 2015 New revision: 395660 URL: https://svnweb.freebsd.org/changeset/ports/395660 Log: When not using OpenSSL from ports, do not try to unmount the chrooted engines directory. PR: 201423 (based on) Submitted by: girgen Sponsored by: Absolight Changes: head/dns/bind910/Makefile head/dns/bind910/files/named.in head/dns/bind99/Makefile head/dns/bind99/files/named.in |
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