[ 
https://issues.apache.org/jira/browse/GERONIMO-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076018#comment-13076018
 ] 

viola.lu commented on GERONIMO-6073:
------------------------------------

comments from commons-daemon 
Mladen Turk added a comment - 01/Aug/11 20:24
Think this will not be possible since we redirect the stdout/stderr before 
loading JVM.
After it is loaded JVM uses those descriptors to write to the console.
The user application if desired should call System.setOut and System.setErr
and manage the log rotation on its own.

Think I'll mark this as WONTFIX unless someone figures out how to do it
from the procrun.

> Rotation and appending of console output when Geronimo is run a windows 
> service
> -------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6073
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6073
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: commands
>    Affects Versions: 2.1.7, 2.2.1
>         Environment: Windows
>            Reporter: Vamsavardhana Reddy
>            Assignee: viola.lu
>         Attachments: append_setting.jpg
>
>
> GERONIMO-4394 provided for running Geronimo as windows service.  The console 
> output STDOUT is directed to geronimosrv.out and STDERR is directed to 
> geronimosrv.err.  If the server is running for long, these files can grow big 
> requiring the server to be stopped.  Also, each time the server is started as 
> service, the files from the previous run are overwritten since the output 
> does not get appended to existing file.  So, if a user is interested in the 
> console output from the previous runs, it is lost.  So, console output 
> rotation and appending to already existing files should be a good improvement 
> for the "Run Geronimo as a Windows service" feature.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to