On Sun, Jun 24, 2012 at 12:41 AM, Angelo Chen angelochen...@gmail.comwrote:
not sure if it got restarted, but the log file name remain the same.
If you are not rotating the log it should stay the same. Use
pshttp://unixhelp.ed.ac.uk/CGI/man-cgi?psto find out the process PID
and check if is the
right, one thing i notice is, when the cpu usage is high, it is the
node that runs forever, not the actual app.js, probably forever is not
the real cpu usage of my app?
On Jun 23, 8:33 am, Oliver Leics oliver.le...@gmail.com wrote:
On Fri, Jun 22, 2012 at 2:54 PM, Angelo Chen
Is your app being restarted in a tight loop during this time?
On Saturday, June 23, 2012 9:16:06 PM UTC-5, Angelo Chen wrote:
right, one thing i notice is, when the cpu usage is high, it is the
node that runs forever, not the actual app.js, probably forever is not
the real cpu usage of my
not sure if it got restarted, but the log file name remain the same.
On Jun 24, 10:29 am, Bradley Meck bradley.m...@gmail.com wrote:
Is your app being restarted in a tight loop during this time?
On Saturday, June 23, 2012 9:16:06 PM UTC-5, Angelo Chen wrote:
right, one thing i notice
El viernes, 22 de junio de 2012 08:54:17 UTC-4, Angelo Chen escribió:
Hi,
I run my node with forever, it works quite well, got two questions:
1) at any given time, there are two node running, that's normal?
forever run in one instance of node.js your app runs in another.
--
Job
