Fails to start in background

[simonexmachina]

If I execute the following using up -n 1 test.js (in the foreground) it behaves as expected, but if I start this in the background using up -n 1 test.js & then the master dies, the workers never output 'started' or 'listening' and eventually commit suicide.

console.log('started');
module.exports = server = require('express').createServer();
server.on('listening', function() {
  console.log('listening');
});

[simonexmachina]

Am I the only person seeing this problem? Or is this an issue for anyone else? I need to be able to run this in the background. Happy to look into it myself, but it'd be nice to get some idea of what might be causing it or where to start.

[simonexmachina]

Still no reply to this issue. Anyone? It's a pretty simple example case, would really appreciate some help with this.

[simonexmachina]

Okay it looks to me that up is abandoned. I'll use something else...

[mjadobson]

+1.

[niclashoyer]

if this abandoned, what are the alternatives?

[simonexmachina]

I'm just using forever to re-launch, and I believe that you can use cluster
to provide the multi-process feature but I haven't done this.

[niclashoyer]

For production environments I'm trying naught for now.