Opened 18 years ago
Closed 18 years ago
#11028 closed defect (fixed)
Stunnel exhausts process limit with default configure options
| Reported by: | d@… | Owned by: | pguyot (Paul Guyot) |
|---|---|---|---|
| Priority: | High | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
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 -uis 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
Change History (5)
comment:1 Changed 18 years ago by macports-dev@…
comment:2 Changed 18 years ago by 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.
comment:3 Changed 18 years ago by d@…
Should probably mention, when I reported this problem I was running on G4 PowerBook.
comment:5 Changed 18 years ago by pguyot (Paul Guyot)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(sorry, just seeing this now, I love MacPorts hosting).
As suggested, I created a new variant +libwrap which is enabled by default.
we could add a +no_server or a +server or a +libwrap... hard to say. what do you think Paul?