Stunnel exhausts process limit with default configure options

[d@…]

Hi there,

Stunnel as it currently exists in MacPorts can fork repeatedly until the default user process limit is reached.

We're currently using stunnel as a client to access imap, smtp and jabber services. After some time, zombie stunnel processes start appearing. The number of zombie stunnels will continue to rise until ulimit -u is reached.

Configuring stunnel with --disable-libwrap seems to prevent stunnel creating zombies. I didn't want to create this as a diff to the Portfile however as people probably run stunnel as a server which makes use of tcpwrappers. What's the correct approach here?

Cheers, Dan

[macports-dev@…]

we could add a +no_server or a +server or a +libwrap... hard to say. what do you think Paul?

[d@…]

I've just upgraded to a MacBook Pro and I don't seem to have the same problem here - no zombie stunnel processes to be seen.

[d@…]

Should probably mention, when I reported this problem I was running on G4 PowerBook.

[d@…]

Sorry - spoke too soon. Forks on Intel also.

[pguyot@…]

(sorry, just seeing this now, I love MacPorts hosting).

As suggested, I created a new variant +libwrap which is enabled by default.