Hi, Michal
The gateway is running an embedded system, no harddisk is available, so it is not possible to add more RAM or swap.
I think it should be caused by some un-tested/un-catched memory allocation failure somewhere in the source code. is there any debug tool can help for this issue? i tried valgrind, but valgrind was killed by the kernel before stunnel for out of memory.
Michal Trojnara wrote:
Zhuang Yuyao wrote:
The gateway machine running stunnel DO NOT have swap! so the available memory is limited to its physical memory = 64M.
That was important! I've added a line to: http://stunnel.mirt.net/perf.html about memory usage.
In your case I'd try: ulimit - n 100 to stop stunnel from openning more than about 50 connections.
Gateway hardware: 80386 compatible cpu (VIA C3 400Mhz); RAM: 64M
What about adding some RAM or swap? It's not really expensive...
Best regards, Mike
stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users