Task #1449 (new)
Opened 15 years ago
Last modified 8 years ago
Windows logging fixes — at Initial Version
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.1 |
| Component: | Deployment | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
See: http://www.zeroc.com/forums/help-center/4507-request-icegrid-icepatch2-demo-example.html#post19973
The stderr/stdout redirection of servers spawned by the IceGrid? node to the node stderr/stdout files unfortunately doesn't work when the IceGrid? node is started as a service (I believe this is because Windows services don't have a console). It only works if the IceGrid? node is started interactively from a console. So instead of setting Ice.StdOut/Ice?.StdErr? in the node configuration file (when the node is started as a Windows service at least), you should consider using IceGrid?.Node.Output to redirect the stderr/stdout of each server to individual files.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
