Package: unbound Version: 1.6.0-3+deb9u1 Severity: normal Tags: d-i Dear Maintainer,
Unbound package version 1.6.0-3+deb9u1 (amd64), which I tested on different machines, provided script "/etc/init.d/unbound", does not explicitly contain PATH declaration, which results in unknown called scripts. This is problem, when (for example) running the script from cron, resulting in this kind of error messages crontab "0 0 * * * /etc/init.d/unbound restart &> /dev/null" stderr: "Restarting DNS server: unbound/etc/init.d/unbound: 55: /etc/init.d/unbound: start-stop-daemon: not found" of course caused by very basic PATH contents when running from CRON >From what I've seen in similar scripts, PATH is declared as part of initial variables, in case of Unbound it is not declared at all. Would you please kindly fix this issue? -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unbound depends on: ii adduser 3.115 ii dns-root-data 2017072601~deb9u1 ii init-system-helpers 1.48 ii libc6 2.27-3 ii libevent-2.0-5 2.0.21-stable-3 ii libfstrm0 0.3.0-1 ii libprotobuf-c1 1.2.1-2 ii libpython3.5 3.5.3-1 ii libssl1.1 1.1.0h-4 ii openssl 1.1.0f-3+deb9u2 ii unbound-anchor 1.6.0-3+deb9u1 unbound recommends no packages. Versions of packages unbound suggests: ii apparmor 2.11.0-3+deb9u2 -- Configuration Files: /etc/apparmor.d/usr.sbin.unbound changed [not included] -- no debconf information
