You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@uima.apache.org by ch...@apache.org on 2015/03/24 15:27:02 UTC

svn commit: r1668907 - /uima/sandbox/uima-ducc/trunk/src/main/admin/stop_ducc

Author: challngr
Date: Tue Mar 24 14:27:01 2015
New Revision: 1668907

URL: http://svn.apache.org/r1668907
Log:
UIMA-4196 Tiny clarification in stop_ducc if the PIDs file got corrupted.

Modified:
    uima/sandbox/uima-ducc/trunk/src/main/admin/stop_ducc

Modified: uima/sandbox/uima-ducc/trunk/src/main/admin/stop_ducc
URL: http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/src/main/admin/stop_ducc?rev=1668907&r1=1668906&r2=1668907&view=diff
==============================================================================
--- uima/sandbox/uima-ducc/trunk/src/main/admin/stop_ducc (original)
+++ uima/sandbox/uima-ducc/trunk/src/main/admin/stop_ducc Tue Mar 24 14:27:01 2015
@@ -60,7 +60,7 @@ class StopDucc(DuccUtil):
         # If despite all that we can't find the pid, we need to run check_ducc
         #        
         if ( not self.pids.has_key(component) ):
-            print "Cannot find PID for component", component, ". Run check_ducc to refresh PIDS and then rerun stop_ducc."
+            print "Cannot find PID for component", component, ". Run check_ducc -p to refresh PIDS and then rerun stop_ducc."
             return
 
         pid = self.pids.get(component)