DO NOT REPLY [Bug 14133] New: - tomcat4 init.d stop command fails process check

[bu...@apache.org]

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=14133>.
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=14133

tomcat4 init.d stop command fails process check

           Summary: tomcat4 init.d stop command fails process check
           Product: Tomcat 4
           Version: 4.1.12
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: greg_fenton@yahoo.com


On my RH 7.3 configuration, the command:

  "ps -aux | grep catalina"

*always* returns no matches whether Tomcat is running or not.

The "stop" command for the /etc/init.d/tomcat4 script loops until it no longer
gets any matches to the above command (well, a more restrictive grep).  This
loop will always exit immediately.

Looking at the "ps" man page, I don't know if there is a work-around.  Possibly:
   "ps -eo user,cmd | grep -v grep | grep tomcat4 | grep java"
but this is not a perfect solution (for example, if the path to "java" is quite
long, there is a chance that "java" won't appear in the cmd)

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>