Package: unbound Version: 1.2.1-2 Severity: minor Before a stone age, unbound required that all paths it sees be in its chroot directory if it's running chrooted.
Quite some time has passed since that. Now it correctly implements all the init stuff, writes pidfiles etc before entering chroot jail. So there's no reason to keep the pidfile in the wrong location which is inside its choroot jail dir. It's time to move the pid file from /var/lib/unbound/unbound.pid to /var/run/unbound.pid where all the other pid files are keept. But with this I'm not sure how to proceed. Note that the PIDFILE variable is used (and initialized too) in the startup script (and may be overwritten in /etc/default/unbound) to point to the old wrong location. Changing init file or especially /etc/default/unbound is something we want to avoid really. And on the other hand, unbound-1.3.0 is out (I'll submit another wishlist bug about this, since I alredy packaged it), which adds unbound-checkconf -o which, in turn, can be used to easily extract options from unbound.conf for situations exactly like this. So in my startup script for unbound-1.3.0 I removed the PIDFILE usage from init script entirely and replaced that variable with `unbound-checkconf -o pidfile` where appropriate. So it looks like the best way is to update to 1.3 and at the same time to move pidfile to /var/run . Thanks. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (990, 'stable'), (60, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.30-x86-64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages unbound depends on: ii adduser 3.110 add and remove users and groups ii libc6 2.7-18 GNU C Library: Shared libraries ii libldns1 1.5.1-1 ldns library for DNS programming ii libssl0.9.8 0.9.8g-15+lenny1 SSL shared libraries unbound recommends no packages. unbound suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
