Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 60857 invoked from network); 15 Nov 2001 10:37:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Nov 2001 10:37:15 -0000 Received: (qmail 22025 invoked by uid 97); 15 Nov 2001 10:35:51 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 22004 invoked by uid 97); 15 Nov 2001 10:35:51 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 21928 invoked from network); 15 Nov 2001 10:35:43 -0000 Message-ID: From: GOMEZ Henri To: Tomcat Users List Subject: RE: STARTUP.SH DOESN'T WORKS FINE Date: Thu, 15 Nov 2001 11:35:42 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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 to be sure your tomcat has nothing to do with user, make it run under low priority profile (it didn't need to be run as root since it didn't open port < 80). In my latest RPM for tomcat 3.3 and tomcat 4.0, I make tomcat's run under tomcat and tomcat4 users :) - Henri Gomez ___[_]____ EMAIL : hgomez@slib.fr (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Pier Fumagalli [mailto:pier@betaversion.org] >Sent: Thursday, November 15, 2001 11:23 AM >To: Tomcat Users List >Subject: Re: STARTUP.SH DOESN'T WORKS FINE > > >On 14/11/2001 07:07 pm, "Nikola Milutinovic" > >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 children to >that shell >> instance >> are sent a HUP signal (Hang UP). A process may choose to >ignore that signal. >> Every well written daemon and server process SHOULD do that >(among other >> things). >> >> >>> Unix provides simple way to around this feature. >>> Simply type the following command: >>> >>> nohup tomcat.sh run & >> >> >> I use "tomcat.sh start" instead of "tomcat.sh run" and so >should Nancy. The >> problem is in Tomcat getting HUP signal, but in loosing a >console, I think. >> >> >>> In this case all 'console output produced by tomcat will >>> appear in a file called 'nohup.out'. >>> >>> The name nohup comes from the days of flaky dialup connections >>> and is short for 'no hang-up'. It is used to >>> prevent a spurious loss of connection (or hang-up) from stopping >>> a process. >> >> Or for instance, I connect to my company, locate a file for >download, place it >> in script, run the script with nohup and disconnect. The >download will go on. > >It must be the window manager, because when I SSH to a Solaris >8 machine, >issue the "tomcat start" and then exit (with "exit"), tomcat >is still up... >The shell doesn't send any weird HUP, at least from remote... > > Pier > > >-- >To unsubscribe: >For additional commands: >Troubles with the list: > -- To unsubscribe: For additional commands: Troubles with the list: