Red Hat Bugzilla – Bug 157048
stunnel server does not run in background if stunnel.conf contains no defined service
Last modified: 2007-11-30 17:07:17 EST
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
This is especially unnerving at boot time, if stunnel is started through
an init script.
Version-Release number of selected component (if applicable):
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
I have sent a proposed fix upstream.
Thanks for your report.