Re: [Wrapper-user] Delaying console output redirection

[Jason R. <jr...@cl...>]

I was wondering if the feature described below is currently planned to
be implemented by tankisoftware developers.  If not I have some interest
in implementing the functionality on my own and submitting a patch if
the necessary modifications are not too great.  Could tankisoftware
developers provide some suggestions on the best way to go about adding
this functionality?

 

To reiterate the plan is to allowing output sent to stdout and stderr to
be printed to the console until the wrapped software signals the wrapper
that it has checked for all error conditions and is now ready to act as
a daemon.  This will allow error messages such as missing configuration
files, or the fact the daemon is already running to immediately notify
the end-user instead of needing to tail the wrapper's log file.

 

Best Regards,

 

Jason

 

________________________________

From: wra...@li...
[mailto:wra...@li...] On Behalf Of Jason
Resch
Sent: Friday, December 07, 2007 1:24 PM
To: wra...@li...
Subject: [Wrapper-user] Delaying console output redirection

 

I'd like to thank tanukisoftware for their wrapper, we find it quite
useful.  The website reports "it does provide a number of properties to
configure how stdout and stderr output to the JVM console is handled",
however after reviewing the online documentation I could not find the
exact feature I was looking for.  My question to this list is whether or
not it is possible to accomplish the following using the wrapper:

 

To start a daemon and allow it report any immediate errors (such as
problems in the configuration) directly to the console.  Then, assuming
there were no immediate issues, daemonize and redirect output.

 

I see several ways this could be done: signaling the wrapper to redirect
output, having the wrapper delay daemonizing for some fixed period of
time, or even simply not redirecting output at all, and then have my
application close stdout and stderr and use logging for the rest of the
application's lifetime.

 

Are any of the above methods possible?

 

Thanks in advance,

 

Jason Resch