Yes I had modified the script (it wouldn't work at all as on node v6.18) I ended up daemonizing my node process using start-stop-daemon from /etc/init.d <https://gist.github.com/715255>, and monitoring resources with monit <http://mmonit.com/monit/> - it tested successfully up to 6000 concurrent connections (I didn't try to hit the limit...running on a small server 256MB RAM)
Still unsure what happened with supervisord or upstart On Wednesday, June 6, 2012 12:33:03 AM UTC-7, mscdex wrote: > > On Jun 6, 2:20 am, Hugues Hardel <[email protected]> wrote: > > Yep, that's a good point, but I was running the process as root in all > > these scenarios. (At least as shown by *ps aux | grep node)* > > I hope you're not using the code in that gist. It's outdated. > > Since it seems like you're doing realtime-y kind of stuff, have you > tried or thought about using socket.io? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
