This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 157048 - stunnel server does not run in background if stunnel.conf contains no defined service
stunnel server does not run in background if stunnel.conf contains no defined...
Status: CLOSED UPSTREAM
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: stunnel (Show other bugs)
4.0
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Miloslav Trmač
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-06 08:59 EDT by David Tonhofer
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-01 07:30:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Tonhofer 2005-05-06 08:59:59 EDT
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 07:30:57 EDT
I have sent a proposed fix upstream.

Thanks for your report.

Note You need to log in before you can comment on or make changes to this bug.