Ubuntu
stunnel4 package

init script for stunnel4 is not lsb-compatible

Bug #882110 reported by c.h. on 2011-10-26

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	stunnel4 (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

The Linux Standards Base requires SysV init scripts to support the 'status' action. That is, I should be able to run '/etc/init.d/stunnel4 status' to find out whether stunnel is running.

See: http://wiki.debian.org/LSBInitScripts.

For certain applications, LSB compatibility is a requirement.

For example, I am using stunnel4 in a corosync cluster. Corosync relies on LSB-compatible init scripts to determine whether a service is running, and to start and stop it on the appropriate node. Without the status target in the init script, corosync fails to recognize whether the service is running, and barfs all over itself.

Thus, I am left to roll my own stunnel4 packages with a corrected init script. Attached is the patch I'm using to the upstream tools/stunnel.init.in file, which could be included in the debian/patches for this package until upstream fixes the bug (I have not yet reported upstream).

Tags:

Revision history for this message

c.h. (wryfi) wrote on 2011-10-26:

stunnel.init.in.patch Edit (1.1 KiB, text/plain)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-11-11:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in stunnel4 (Ubuntu):
status:	New → Confirmed

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2011-11-12:

The attachment "stunnel.init.in.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags:

added: patch

Revision history for this message

Andrew Schulman (andrex) wrote on 2013-12-31:

Would it be possible to get this bug fixed? It's two years old, and a simple patch has been posted to fix it that looks correct. Thanks, Andrew.