[stunnel-users] New libwrap code

[Randy McMurchy]

Hi all,

My apologies if this has been discussed (I've reviewed the
archives since 4.21 was released), and if so please just
point me in the right direction.

I read in some of the messages there's been a revamp
(overhaul, changes, whatever) of the libwrap code in
Stunnel-4.21. I'm not having any issues using the new
version, however, I'm seeing it spawn 5 processes where
in every other version I've used in the past there has
always only been one process spawned. Here's what I see:

root      3408     1  0 17:50 pts/10   00:00:00 /usr/bin/stunnel
root      3409     1  0 17:50 pts/10   00:00:00 /usr/bin/stunnel
root      3410     1  0 17:50 pts/10   00:00:00 /usr/bin/stunnel
root      3411     1  0 17:50 pts/10   00:00:00 /usr/bin/stunnel
root      3412     1  0 17:50 pts/10   00:00:00 /usr/bin/stunnel
stunnel   3413     1  0 17:50 ?        00:00:00 /usr/bin/stunnel

Is this a product of the new libwrap code? I turned debug
messages WAY up and I see over and over startup messages
for all 5 processes. Example of one:

2008.03.25 17:50:24 LOG5[3407:3082803904]: stunnel 4.21 on i686-pc-linux-gnu with OpenSSL 0.9.8e 23 Feb 2007
2008.03.25 17:50:24 LOG5[3407:3082803904]: Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv4 Auth:LIBWRAP
2008.03.25 17:50:24 LOG6[3407:3082803904]: file ulimit = 1024 (can be changed with 'ulimit -n')
2008.03.25 17:50:24 LOG6[3407:3082803904]: poll() used - no FD_SETSIZE limit for file descriptors
2008.03.25 17:50:24 LOG5[3407:3082803904]: 500 clients allowed
2008.03.25 17:50:24 LOG7[3407:3082803904]: FD 9 in non-blocking mode
2008.03.25 17:50:24 LOG7[3407:3082803904]: FD 10 in non-blocking mode
2008.03.25 17:50:24 LOG7[3407:3082803904]: FD 11 in non-blocking mode
2008.03.25 17:50:24 LOG7[3407:3082803904]: SO_REUSEADDR option set on accept socket
2008.03.25 17:50:24 LOG7[3407:3082803904]: swat bound to 0.0.0.0:904
2008.03.25 17:50:24 LOG7[3413:3082803904]: Created pid file /run/stunnel.pid
2008.03.25 17:50:42 LOG7[3413:3082803904]: swat accepted FD=12 from 192.168.11.212:1535
2008.03.25 17:50:42 LOG7[3413:3086076816]: swat started
2008.03.25 17:50:42 LOG7[3413:3086076816]: FD 12 in non-blocking mode
2008.03.25 17:50:42 LOG7[3413:3086076816]: Waiting for a libwrap process
2008.03.25 17:50:42 LOG7[3413:3086076816]: Acquired libwrap process #0
2008.03.25 17:50:42 LOG7[3413:3086076816]: Releasing libwrap process #0
2008.03.25 17:50:42 LOG7[3413:3086076816]: Released libwrap process #0
2008.03.25 17:50:42 LOG7[3413:3086076816]: swat permitted by libwrap from 192.168.11.212:1535
2008.03.25 17:50:42 LOG5[3413:3086076816]: swat accepted connection from 192.168.11.212:1535

When I connect to swat (Samba config tool) it again goes
through a process of using all 5 of the system processes.
Sorry for being so verbose here. My question is:

Has something changed so that there is more than one
process spawned (and used) when Stunnel is started?

Any help would be appreciated.

--
Randy