RE: [Wrapper-user] wrapper as daemon on un*x

[Pritchard, S. <SP1...@te...>]

I am using Solaris 9 and did an explicit test to confirm I was not seeing
Rajiv's reported behavior yesterday.  I am not seeing it, but then again, I
am using bash as my shell and his note said it only occurs when you use sh
as your shell.

Sean

-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...]
Sent: Friday, January 17, 2003 12:20 PM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper as daemon on un*x


Rajiv,
Thanks for this patch. But I have some questions.

I have not had access to a Solaris machine for a while so I can not
verify the
behavior now. On Linux, it appears to work if I telnet to the box, start
an app
and then log off. The wrapper process will still be running when I come
back at
a later date. Maybe this is just a Solaris issue? I am surprised that no
other
users have ever said anything about this before.

Any solaris users out there have any comments on this?

I have no problem adding this feature. Especially since it is all
implemented. :-)
I am just curious as to why others have not run into this. Or if they
have, how
they have been working around it.

Also a question. With this patch. Are you still able to capture stdout
and stderr
output from the Java process and log them to the file. It looks like wrapper
console output is being thrown away. Which is fine for a daemon process.

Cheers,
Leif




-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user