Opened 7 years ago

Closed 4 years ago

#283 closed Feature Wish (fixed-external)

Small improvements to RHEL init script

Reported by: Simon Matter Owned by: Samuli Seppänen
Priority: minor Milestone:
Component: Packaging Version: OpenVPN git master branch (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords: volunteer
Cc:

Description

The small patch adds two features which makes life easier in our situation:

1) change the order when calling openvpn to --cd $work --config $c. That makes it possible to add another 'cd' to the config file. I didn't expect it but it really matters.

2) skip empty .conf and .sh files so nothing is called. That way we can deploy an empty dummy .conf file on hosts where no openvpn connection should run and still configure the service normally.

Thanks,
Simon

Attachments (1)

openvpn-2.3.1-init.patch (784 bytes) - added by Simon Matter 7 years ago.

Download all attachments as: .zip

Change History (8)

Changed 7 years ago by Simon Matter

Attachment: openvpn-2.3.1-init.patch added

comment:1 Changed 7 years ago by Samuli Seppänen

Hmm, yes, we do have RedHat init scripts in the main OpenVPN Git repository. Currently I'm building tons of Debian/Ubuntu packages and they too require a bunch of control files. Whether these should be stored in the main Git repository like RedHat init scripts are now, or kept separate, like Windows packaging files, is a matter of debate.

Whether we want to create packages for RedHat derivatives is also not clear. The RPMForge repos, for example, do a fairly good job in keeping up with latest OpenVPN releases, contrary to, say, Ubuntu and Debian. If we want to provide development snapshots then having internal RedHat packages available does make sense.

Any opinions?

comment:2 Changed 7 years ago by Samuli Seppänen

Component: InstallationPackaging
Owner: set to Samuli Seppänen

comment:3 Changed 7 years ago by Gert Döring

Samuli, so what to do wit this one? Have we decided where "package building stuff" goes to? (This applies to #9 as well)

comment:4 Changed 5 years ago by Gert Döring

ping?

comment:5 Changed 5 years ago by Samuli Seppänen

Keywords: volunteer added
Priority: trivialminor
Version: 2.2.2git master branch

Packaging is currently handled outside openvpn:

To maintain consistency I'd prefer moving RPM packaging out of the main OpenVPN repository.

It would be great to have a volunteer that could maintain the RPM spec files, from which official and non-official RPM builds could be generated.

comment:6 Changed 5 years ago by David Sommerseth

Fedora and Fedora EPEL .spec files can be found here: http://pkgs.fedoraproject.org/cgit/openvpn.git/

Those are actively maintained by the Fedora packagers. And they are the starting point when OpenVPN is decided to be packaged for RHEL as well.

Each branch in this repo targets a specific Fedora/EPEL release.

comment:7 Changed 4 years ago by David Sommerseth

Resolution: fixed-external
Status: newclosed

AFAICT, this has been resolved for Fedora EPEL 6 (RHEL 6), which uses upstart based init.d scripts.

http://pkgs.fedoraproject.org/cgit/rpms/openvpn.git/tree/openvpn.init?h=el6

Even though RHEL 7 is systemd based, this also seems to have the suggested order.

http://pkgs.fedoraproject.org/cgit/rpms/openvpn.git/tree/openvpn@.service?h=epel7

For a fix in the package distributed through ordinary RHEL6 channels, this must be fixed by Red Hat through their bugzilla. For RHEL7, OpenVPN is not shipped by Red Hat and you must use Fedora EPEL.

Note: See TracTickets for help on using tickets.