Naught causing too man fork()'s for Upstart to track

Hi,

I'm consistently seeing Naught run with a PID higher than the one Upstart is trying to track. I have tried both `expect fork` and `expect daemon` and I am seeing Upstart report `start/running, process 3005` but then seeing `start_daemon.js` running with a process ID 2 or 3 higher (in this particular case 3007 with expect fork being used).

I'm using Upstart to start my node app with naught when the system boots. I can post my full upstart conf file if it would help.

If I remove the `start on` from the conf and therefor have to start the service manually it works the first time but then if I do a `service app restart` (or a stop and then a start as separate commands) I end up back on the above pattern.

I appreciate you might not want to get into the vagaries of Upstart but if you have any ideas of what might be causing the behaviour I'm seeing and you can give me a jumping off point I'm happy to do some digging and leg work.

Many thanks for any help or ideas you may have.