> > Thanks for the suggestion, although unfortunately I don't think that would > work for my real scenario. I'm spawning long running tasks, which may > outlive the process that spawned them (which is why I'm directing the > output into a file). Presumably these streams would all stop working / die > when my parent process ends.
You could just spawn it detached (check the options for spawn<http://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options>) but you'd need to make sure you don't spawn duplicates every time your app boots… but that sounds like copmlexity for a solved problem. If you want to ensure the streams keep living, then keep them alive the same way you would anything else, as its own standalone daemon, managed by upstart or monit or whatever. -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
