So after much fiddling I managed to get some C applications (web servers) compiling as rump kernels, specifically thttpd and mathopd
One-off curl requests to the server i.e curl 192.168.1.120 work fine and return the expected index.html When I use the siege benchmarking tool to hit the server harder, after maybe a few hundred or thousand successful requests, the siege client starts returning socket errors. Here is an extract from a much longer output: HTTP/1.1 200 0.00 secs: 216 bytes ==> GET / HTTP/1.1 200 0.00 secs: 216 bytes ==> GET / HTTP/1.1 200 0.00 secs: 216 bytes ==> GET / [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] unable to write to socket sock.c:581: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer [error] socket: read error Connection reset by peer sock.c:479: Connection reset by peer The notable thing here is that the same problem occured on both web servers. Anyone got any ideas what might be behind the socket errors? thanks as
