maccman
pid file
I'm wanting to monitor juggernatu and restart it fairly frequently because of the memory leaks (~60MB after 5 hours, ~100MB after 12 hours). I haven't yet tried the latest git version to see if it's better... I'd still like to be able to monitor the pid though.
Is there any way to have it write a pid file for it's demonized process saved somewhere? I poked around in the source but aren't familiar with node.js enough to know where it would go.
Maybe the solution is to solve the memory leaks? Any idea where they're occurring?
On Thu, Jun 23, 2011 at 11:52 AM, inspire22 < [email protected]>wrote:
I'm wanting to monitor juggernatu and restart it fairly frequently because of the memory leaks (~60MB after 5 hours, ~100MB after 12 hours). I haven't yet tried the latest git version to see if it's better... I'd still like to be able to monitor the pid though.
Is there any way to have it write a pid file for it's demonized process saved somewhere? I poked around in the source but aren't familiar with node.js enough to know where it would go.
Reply to this email directly or view it on GitHub: https://github.com/maccman/juggernaut/issues/82
Alex MacCaw
+12147175129 @maccman
http://alexmaccaw.co.uk | http://www.leadthinking.com | http://socialmod.com
I tried updating to the latest version, but they're still there. I'm not fam. with node.js's garbage collection enough to try to track it down, but it seems roughly linear with the # messages sent, so perhaps it's not cleaning them for some reason.