tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21993] New: - startup.sh needs nohup to suceed
Date Wed, 30 Jul 2003 14:13:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21993>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21993

startup.sh needs nohup to suceed

           Summary: startup.sh needs nohup to suceed
           Product: Tomcat 4
           Version: 4.1.24
          Platform: Other
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: akrueger@tes.zv.mmo.de


I've tried to run (a script that in turn runs) "startup.sh"
in the "compile" window of Emacs.

This will cause Tomcat to not come up.

I have than tried to include a sleep 10.  That causes Tomcat to run partially,
as I can see from the logs that are generated, but than it again fails.

Running startup.sh under "nohup" helps.

Appearently, startup.sh just triggers Tomcat to start,
then exists.  When the parent process of startup.sh happens to be teared down,
that causes a "SIGHUP" signal to be send to the Tomcat startup process.

My suggestion:

Either make startup.sh a script that runs for as long as Tomcat runs,
or truely daemonize right up front.

(This is somewhat related to bug 11753.)

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message