Jason Mitchell <jmitchel%bigjar.com@localhost> writes:
I've been dealing with a problem where stunnel segfaults on every
connection where OCSP stapling is required. The stunnel folks just got
back to me and there's an easy fix -- add stack = 131072 and the
problem goes away. There going to fix it in the next release. Should
we put a warning message on the stunnel package in pkgsrc advising
people to add this line to their stunnel.conf file?
It would make sense to add this to the example config file that the
package does or should install.
Or, to see what their fix is and apply it as a patch. I wonder if their
approach is to increase the limit, or to be less consuming of resources.
ulimit -s shows
stack size (kbytes, -s) 4096
on a system where I have no memory of messing with stack size.
That's 4 MB, which seems like quite a lot of stack.
I wonder if they really mean 128 MB of stack?