|
From: Leif M. <le...@ta...> - 2007-12-07 21:15:04
|
Jason, Are you meaning on UNIX? That is great idea. I often find myself starting an application and then tailing the wrapper.log to make sure it started normally. I will think about how to do this. Cheers, Leif Jason Resch wrote: > > 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 > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |