Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-26 Thread Michael Banck
On Sat, Feb 26, 2011 at 05:54:23PM +0100, Sean Finney wrote: > On Sat, 2011-02-26 at 14:32 +0100, Michael Banck wrote: > > > > > > The right way to do this is, IMNSHO, what systemd does and just have > > > init handle starting and stopping the job. That ensures there's no > > > inconsistency betw

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-26 Thread Sean Finney
On Sat, 2011-02-26 at 14:32 +0100, Michael Banck wrote: > > > > The right way to do this is, IMNSHO, what systemd does and just have > > init handle starting and stopping the job. That ensures there's no > > inconsistency between boot-time starting and starting later by hand. > > Right, but it m

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-26 Thread Raphael Geissert
Timo Weingärtner wrote: >> Maybe start-stop-daemon should have an option to delete all but a >> specified set of environment variables, maybe even enabled by default. > > service (8) does that already. Exactly, and it is supposed to be the interface used by humans to start/stop/etc services sinc

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-26 Thread Olaf van der Spek
On Fri, Feb 25, 2011 at 9:55 AM, Peter Palfrader wrote: > We should probably start a campaign in Debian to have all init scripts > sanitize the environment of daemons they start. > > I usually run initscripts using "env -i /etc/init.d/$foo start" to > achieve exactly that, but ideally the init scr

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-26 Thread Michael Banck
On Fri, Feb 25, 2011 at 11:43:50AM +0100, Tollef Fog Heen wrote: > ]] Timo Weingärtner > > | service (8) does that already. > > The right way to do this is, IMNSHO, what systemd does and just have > init handle starting and stopping the job. That ensures there's no > inconsistency between boot-

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Don Armstrong
On Fri, 25 Feb 2011, Don Armstrong wrote: > On Fri, 25 Feb 2011, Peter Palfrader wrote: > > Maybe start-stop-daemon should have an option to delete all but a > > specified set of environment variables, maybe even enabled by > > default. > > The problem is in cases where you actually want to pass e

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Don Armstrong
On Fri, 25 Feb 2011, Peter Palfrader wrote: > Maybe start-stop-daemon should have an option to delete all but a > specified set of environment variables, maybe even enabled by > default. The problem is in cases where you actually want to pass environmental variables to the daemon from within the i

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Tollef Fog Heen
]] Timo Weingärtner | service (8) does that already. The right way to do this is, IMNSHO, what systemd does and just have init handle starting and stopping the job. That ensures there's no inconsistency between boot-time starting and starting later by hand. -- Tollef Fog Heen UNIX is user fri

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Timo Weingärtner
Am Freitag, 25. Februar 2011 schrieb Peter Palfrader: > On Thu, 10 Feb 2011, Ben Hutchings wrote: > > Package: bind9 > > Version: 1:9.7.2.dfsg.P3-1.1 > > > > I'm not sure whether this is a bug or my own configuration error. > > > > In interactive shells, I set $OPENSSL_CONF to point to the config

Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set

2011-02-25 Thread Peter Palfrader
On Thu, 10 Feb 2011, Ben Hutchings wrote: > Package: bind9 > Version: 1:9.7.2.dfsg.P3-1.1 > I'm not sure whether this is a bug or my own configuration error. > > In interactive shells, I set $OPENSSL_CONF to point to the configuration > file for my local CA. BIND should not use this, and indeed