Bug#784790: openvpn: wrong condition in init-script

2015-07-14 Thread Alexander Dreweke
Hi > Are you sure you're using sysv's init script and not systemd's service? > If you're using the latter you may have to override openvpn@.service in > order to remove the --daemon option. Remember to issue a "systemctl > daemon-reload". You are right, I'm using systemd. I was so sure that the

Bug#784790: openvpn: wrong condition in init-script

2015-07-06 Thread Alberto Gonzalez Iniesta
On Wed, Jul 01, 2015 at 02:43:02PM +0200, Alexander Dreweke wrote: > Hi > > >You sure? > > [...] > > >Since when "0 is evaluated to false" in a shell script? > Your right. 0 does not evaluate to false. Never the less I do get the > reported message. > > All daemons config files contain a line d

Bug#784790: openvpn: wrong condition in init-script

2015-07-01 Thread Alexander Dreweke
Hi You sure? [...] Since when "0 is evaluated to false" in a shell script? Your right. 0 does not evaluate to false. Never the less I do get the reported message. All daemons config files contain a line defining the daemon name, but the openvpn processes are given the --daemon option.

Bug#784790: openvpn: wrong condition in init-script

2015-07-01 Thread Alberto Gonzalez Iniesta
On Fri, May 08, 2015 at 10:19:25PM +0200, Alexander Dreweke wrote: > Package: openvpn > Version: 2.3.4-5 > Severity: normal > > Dear Maintainer, > > I'm using the daemon option in my openvpn settings, while investigating > an unrelated openvpn problem I've noticed the following error messages > i

Bug#784790: openvpn: wrong condition in init-script

2015-05-08 Thread Alexander Dreweke
Package: openvpn Version: 2.3.4-5 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, I'm using the daemon option in my openvpn settings, while investigating an unrelated openvpn problem I've noticed the following error messages in the daemon.log: May 8 21:59:53 foo