| Summary: | Running orion in background stumbling blocks and suggested solution | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Adrian Aichner <adrian.aichner> | ||||
| Component: | Server | Assignee: | Project Inbox <orion.server-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 1.0 | ||||||
| Target Milestone: | 5.0 RC1 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Adrian Aichner
The main reason for the console is that with no console there is no way to do an orderly shutdown of the server. I.e., the next section in the admin guide says to invoke "stop" on the console to shutdown. At the very least we can update the admin guide to describe both "interactive" and "background" modes of running. Perhaps a HUP signal should do same action as osgi close command? At any rate current orion.ini will conflict with background Operation. The addition of http://wiki.eclipse.org/Orion/Server_admin_guide#Running_disconnected_from_a_shell_on_Unix which works fine for me on my local server running HEAD master closes this bug for me. |