Re: STARTUP.SH DOESN'T WORKS FINE

> Hi again! > And thank you very much to all of you who had been sending some advice!! > > I tried to start Tomcat with the following sentence: > > "tomcat.sh start &" There is no need for "&" with "start", it already has "&" in the script. > And it didn't work again... > I'm going t

Re: STARTUP.SH DOESN'T WORKS FINE

Hi again! And thank you very much to all of you who had been sending some advice!! I tried to start Tomcat with the following sentence: "tomcat.sh start &" And it didn't work again... I'm going to try with "nohup"... When I work with the server (Solaris) I open a terminal window and I close it

Re: STARTUP.SH DOESN'T WORKS FINE

> If you want a process to be independant from user connection, > disconnection on a Unix boxes (and more generally on any system), > you should make it run as a service. > > For example on Linux, you make it run at init time via > script in /etc/rc.d/init.d/. And suppose it just blocks

Re: STARTUP.SH DOESN'T WORKS FINE

> > Good point. > > > > "Every well written daemon" will do the following: > > > > 1. parse input and complain if necessary > > 2. spawn a child and exit > > 3. a child will close STDIN, STDOUT, STDERR > > 4. a child will catch/ignore SIGHUP, SIGTERM, ... > > 5. a child will spawn a daem

RE: STARTUP.SH DOESN'T WORKS FINE

List >Subject: Re: STARTUP.SH DOESN'T WORKS FINE > > >On 14/11/2001 07:07 pm, "Nikola Milutinovic" ><[EMAIL PROTECTED]> >wrote: > >> Tom Drake wrote: >> >>> This has nothing to do with tomcat. It is standard unix behavior. >>> Wh

Re: STARTUP.SH DOESN'T WORKS FINE

"Nikola Milutinovic" <[EMAIL PROTECTED]> wrote: > Good point. > > "Every well written daemon" will do the following: > > 1. parse input and complain if necessary > 2. spawn a child and exit > 3. a child will close STDIN, STDOUT, STDERR > 4. a child will catch/ignore SIGHUP, SIGTERM, ... > 5. a

Re: STARTUP.SH DOESN'T WORKS FINE

On 14/11/2001 07:07 pm, "Nikola Milutinovic" <[EMAIL PROTECTED]> wrote: > Tom Drake wrote: > >> This has nothing to do with tomcat. It is standard unix behavior. >> When a user logs out, all processes created by that user are killed. > > > No, when a user logs out all processes that are childr

Re: STARTUP.SH DOESN'T WORKS FINE

On 22/10/2001 03:54 pm, "Nancy Crisostomo Martinez" <[EMAIL PROTECTED]> wrote: > Hello everybody! > I hope you could help me, please.. > > Actually, I'm begining to use Tomcat, and I have a succeded start > because it still works PERFECT to me... > But muy problem is very strange : > I installed

Re: STARTUP.SH DOESN'T WORKS FINE

> | Tom Drake wrote: > | > | > This has nothing to do with tomcat. It is standard unix behavior. > | > When a user logs out, all processes created by that user are killed. > | > | > | No, when a user logs out all processes that are children to that shell > instance > | are sent a HUP signa

Re: STARTUP.SH DOESN'T WORKS FINE

> > Every well written daemon and server process SHOULD do that > > (among other things). > > But you need to remember that you are not running Tomcat, you are running > Java - that's a big difference. And it limits what is possible. Good point. "Every well written daemon" will do the

Re: STARTUP.SH DOESN'T WORKS FINE

--- Tom Drake <[EMAIL PROTECTED]> wrote: > > Effectively the process is killed. I think we are > saying the same thing. > As far as I know, there's no way to receive SIGHUP > (or any other Unix > signal) > in your java code anyway. > It is possible to register a shutdown hook which is executed

Re: STARTUP.SH DOESN'T WORKS FINE

Hi Nancy, This is what happens under Linux: 1. Switch to a virtual console and login 2. execute startup.sh (Tomcat is running) 3. exit from shell 4. Login and Tomcat is still running. So I have daemon behaviour under Linux. -Janek --- Nancy Crisostomo Martinez <[EMAIL PROTECTED]> wrote: >

RE: STARTUP.SH DOESN'T WORKS FINE

Sent: Monday, October 22, 2001 8:55 AM To: Tomcat_Users Subject: STARTUP.SH DOESN'T WORKS FINE Hello everybody! I hope you could help me, please.. Actually, I'm begining to use Tomcat, and I have a succeded start because it still works PERFECT to me... But muy problem is very strange

Re: STARTUP.SH DOESN'T WORKS FINE

- Original Message - From: "Nikola Milutinovic" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 11:07 AM Subject: Re: STARTUP.SH DOESN'T WORKS FINE | Tom Drake wrote: | | > This has nothin

RE: STARTUP.SH DOESN'T WORKS FINE

> -Original Message- > From: Nikola Milutinovic [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 14, 2001 2:07 PM > To: Tomcat Users List > Subject: Re: STARTUP.SH DOESN'T WORKS FINE > > > Every well written daemon and server process SHOULD d

Re: STARTUP.SH DOESN'T WORKS FINE

Tom Drake wrote: > This has nothing to do with tomcat. It is standard unix behavior. > When a user logs out, all processes created by that user are killed. No, when a user logs out all processes that are children to that shell instance are sent a HUP signal (Hang UP). A process may choose to

Re: STARTUP.SH DOESN'T WORKS FINE

m: "Nancy Crisostomo Martinez" <[EMAIL PROTECTED]> To: "Tomcat_Users" <[EMAIL PROTECTED]> Sent: Monday, October 22, 2001 7:54 AM Subject: STARTUP.SH DOESN'T WORKS FINE | Hello everybody! | I hope you could help me, please.. | | Actually, I'm begining to use

STARTUP.SH DOESN'T WORKS FINE

Hello everybody! I hope you could help me, please.. Actually, I'm begining to use Tomcat, and I have a succeded start because it still works PERFECT to me... But muy problem is very strange : I installed Tomcat to Solaris 8, and when I start it (startup.sh | tomcat.sh start ) it starts, but when