>>If the problem is within nginx, then running nginx the same way in on a >>regular system should exhibit the same behavior, right?
OK so I added these two lines to /etc/nginx/nginx.conf and started the nginx service (which of course ran in the foreground). master_process off; daemon off; I was following Antii’s line of thinking which I read as….. if the problem is because it is running with master_process or daemon off then the same thing should happen in a rump and a “normal” environment. Here is the result: root@contiki:/home/ubuntu/temp# siege -c10 -b -t20s -i http://localhost/logo150.png ** SIEGE 3.0.5 ** Preparing 10 concurrent users for battle. The server is now under siege... Lifting the server siege... done. Transactions: 252314 hits Availability: 100.00 % Elapsed time: 19.85 secs Data transferred: 1563.82 MB Response time: 0.00 secs Transaction rate: 12711.03 trans/sec Throughput: 78.78 MB/sec Concurrency: 9.73 Successful transactions: 252314 Failed transactions: 0 Longest transaction: 0.03 Shortest transaction: 0.00 FILE: /var/log/siege.log You can disable this annoying message by editing the .siegerc file in your home directory; change the directive 'show-logfile' to false.
