Bug 157048

Summary:	stunnel server does not run in background if stunnel.conf contains no defined service
Product:	Red Hat Enterprise Linux 4	Reporter:	David Tonhofer <bughunt>
Component:	stunnel	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED UPSTREAM	QA Contact:	Brian Brock <bbrock>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-06-01 11:30:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Tonhofer 2005-05-06 12:59:59 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:
If you define an /etc/stunnel/stunnel.conf with stunnel defined as server
(i.e. no "client = yes" entry) and no services at all, then start stunnel,
stunnel will never return nor will it fork. Instead it will just sit in the
foreground. 

This is especially unnerving at boot time, if stunnel is started through
an init script.


Version-Release number of selected component (if applicable):
stunnel-4.05-3

How reproducible:
Always

Steps to Reproduce:
1. Create /etc/stunnel/stunnel.conf with stunnel defined as server (i.e.
   no "client = yes" entry) and no services
2. Start stunnel
3. Stunnel runs in foreground and does nothing
  

Actual Results:  Stunnel runs in foreground and does nothing

Expected Results:  Stunnel should complain and terminate

Additional info:

Comment 1 Miloslav Trmač 2005-06-01 11:30:57 UTC

I have sent a proposed fix upstream.

Thanks for your report.