Build seemed to be stalled after the examples. Looking at my process list, I noticed two stunnel processes and syslog-ng using a lot of cpu ressources. Looking at the log files /var/log/daemon.log grew to 1.7G polluted with the following line: Jul 30 09:56:18 iglu stunnel: warning: can't get client address: Bad file descriptor I'd say it is not expected too much that the test script does not try to connect endlessly...
I think strictly this is a stunnel bug, see: http://groups.google.com/group/mailing.unix.stunnel-users/browse_thread/thread/3cd71c899f1b2921/15aa00f11a2a27cf?lnk=raot and http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/176409.html Can you grab the patch from ftp://stunnel.mirt.net/stunnel/libwrap_shutdown.patch apply it to stunnel and see if it goes away?
thinking this is probably fixed. - stunnel security fix occured in July, reopen if this isn't the case
