Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#15673 - [openvpn] rc from 2.1_rc19-1 is broken

Attached to Project: Arch Linux
Opened by Jakub Schmidtke (sjakub) - Friday, 24 July 2009, 23:13 GMT
Last edited by Thomas Bächler (brain0) - Thursday, 01 October 2009, 15:22 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



I have installed openvpn from testing, and it includes rc.d script - older versions didn't have it.

But the script is broken:
# /etc/rc.d/openvpn start
:: Starting OpenVPN ... whatever /etc/rc.d/openvpn: line 16: success: command not found [BUSY]

Also, it tries to run ALL /etc/openvpn/*.conf files.
There is a script, on Arch's wiki (,
that works and behaves better - it only starts those networks, that are specified
in /etc/rc.conf file. I have a number of OpenVPN configurations, some of them I start
only when I need them. Some also ask me to provide username and password - new openvpn script
just dumps those requests on the screen, which isn't pretty either.
I could, of course, move those config files somewhere else, but I think the way the wiki script works
is just better.

Package: openvpn-2.1_rc19-1
This task depends upon

Closed by  Thomas Bächler (brain0)
Thursday, 01 October 2009, 15:22 GMT
Reason for closing:  Fixed
Comment by Thomas Bächler (brain0) - Saturday, 25 July 2009, 00:24 GMT
The "success" thing is a typo:

The behaviour with loading every .conf file is much simpler to manage IMO. Having extra configuration to edit is not necessary here. If you don't want the configuration to be launched, just call it "whatever.conf.noauto" or anything else not ending with .conf. Having a meta-configuration file for knowing which configurations to load is redundant.
Comment by Gerhard Brauer (GerBra) - Friday, 14 August 2009, 10:49 GMT
Thomas, could you explain why we use Beta/RC versions in [core]?
(We also have some other reports where this version breaks setups which works fine with stable version).
Comment by Thomas Bächler (brain0) - Friday, 14 August 2009, 11:53 GMT
The 2.0.X branch is unmaintained and the 2.1 branch has been working 100% stable for months for me. Another reason is that not a single developer uses the 2.0.X version, but I use 2.1 extensively.

If there is breakage, people should report separate bugs. However, most breakage should be one of the few incompatibilities between 2.0 and 2.1 which can be worked around, there is a list of incompatibilities somewhere on their homepage.