Your message dated Wed, 27 Nov 2013 22:21:01 +0100
with message-id <[email protected]>
and subject line Re: Bug#682615: initscripts: doesn´t seem to take additional
arguments to openvpn initscript
has caused the Debian Bug report #682615,
regarding initscripts: doesn´t seem to take additional arguments to openvpn
initscript
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
682615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682615
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 44-4
Severity: important
Dear Maintainer,
I tried to start an OpenVPN and got:
merkaba:~> /etc/init.d/openvpn start teamix
[ ok ] Starting openvpn (via systemctl): openvpn.service.
I should have been asked some credentials, but I wasn´t. OpenVPN is
not running.
That seems to be the same result as when running the initscript without
additional argument.
merkaba:~> /etc/init.d/openvpn start
[ ok ] Starting openvpn (via systemctl): openvpn.service.
The OpenVPN initscript uses the additional argument to determine which
VPN to bring up. Without argument it brings anything up that I told it
to bring up by default – which is none in my setup.
I think I will workaround by running openvpn with --config directly.
But for full initscript compatibility I think it is good to fix this.
Thanks,
Martin
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (120, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5.0-tp520 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii dpkg 1.16.8
ii initscripts 2.88dsf-29
ii libacl1 2.2.51-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-35
ii libcap2 1:2.22-1.1
ii libcryptsetup4 2:1.4.3-2
ii libdbus-1-3 1.6.2-2
ii libkmod2 9-1
ii liblzma5 5.1.1alpha+20120614-1
ii libpam0g 1.1.3-7.1
ii libselinux1 2.1.9-5
ii libsystemd-daemon0 44-4
ii libsystemd-id128-0 44-4
ii libsystemd-journal0 44-4
ii libsystemd-login0 44-4
ii libudev0 175-3.1
ii libwrap0 7.6.q-23
ii udev 175-3.1
ii util-linux 2.20.1-5.1
Versions of packages systemd recommends:
ii libpam-systemd 44-4
Versions of packages systemd suggests:
ii python 2.7.3-1
ii python-cairo 1.8.8-1+b2
ii python-dbus 1.1.1-1
ii systemd-gui 44-4
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Martin,
Martin Steigerwald <[email protected]> writes:
>> There's no way to «fix» this within systemd, it's simply done in a
>> different way.
>
> Hmmm, okay. So then close this?
Closing as per submitter’s request.
--
Best regards,
Michael
--- End Message ---
