/etc/unbound/syslogd overrides settings in /etc/default/syslogd
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unbound (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: unbound
This is my first bug report, so apologies if I'm not doing it right.
Ubuntu 9.04 , Unbound 1.2.1-0ubuntu1
I have
SYSLOGD="-r"
in /etc/default/
I also have unbound installed, which has
SYSLOGD="-a /var/lib/
in /etc/unbound/
I think that /etc/unbound/
SYSLOGD="$SYSLOGD -a /var/lib/
so that both options can be used.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelMo
Package: unbound 1.2.1-0ubuntu1
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: unbound
Uname: Linux 2.6.28-15-generic i686
Related branches
| Paul Lettington (paul-lettington) wrote | #1 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in unbound (Ubuntu): | |
| status: | New → Fix Released |
This bug was fixed in the package unbound - 1.3.3-1ubuntu1
---------------
unbound (1.3.3-1ubuntu1) karmic; urgency=low
* Merge from debian unstable, remaining changes (LP: #458226):
- Version build-dep on libldns-dev to (>=1.4.0)
- Added util/configpars
debian/
* Dropped Ubuntu specific changes for running in a chroot as more trouble
than they are worth
- Also solves LP: #445414
unbound (1.3.3-1) unstable; urgency=low
* New upstream release.
* Drop .la file from libunbound-dev; closes: #541640.
unbound (1.3.2-1) unstable; urgency=low
* New upstream release.
unbound (1.3.0-1) unstable; urgency=low
* New upstream release; closes: #533613.
* Move pid file to /var/run; closes: #533611.
* Use "unbound-checkconf -o pidfile" in init script to determine pid file
location (thanks Michael Tokarev).
unbound (1.2.1-2) unstable; urgency=low
* Closes: #527753, #509535.
unbound (1.2.1-1) unstable; urgency=low
* New upstream release.
* Remove init script chroot setup.
-- Scott Kitterman <email address hidden> Thu, 22 Oct 2009 09:55:28 -0400