Bugzilla – Full Text Bug Listing
| Summary: | Long-running node applications are hard to identify | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> |
| Component: | Node | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |
1. Create a file and make it into a simple long-running Node application with some code like this: require('http').createServer(function (req, res) { res.writeHead(200); res.end("hello"); }).listen(8082); 2. Go to Shell page and use `node start` to run the app. 3. Use `node list` to print out what applications are running. Each entry in the list only shows a PID and some URLs. There's nothing that would help you remember which app is which. It should show the path of the module being run, or something similar.