https://bz.apache.org/bugzilla/show_bug.cgi?id=58626
--- Comment #21 from Konstantin Kolinko <knst.koli...@gmail.com> --- (In reply to Michael Osipov from comment #20) > (In reply to Konstantin Kolinko from comment #19) > > I think this may change the meaning of pid value in $CATALINA_PID file. I > > think that it will be the process id of nohup process instead of java one. > > > > Known uses of pid value: > > > > - forcibly terminating Tomcat with shutdown.sh -force > > > > echo "Killing Tomcat with the PID: $PID" > > kill -9 $PID > > > > - asking java for a thread dump > > > > echo "To aid diagnostics a thread dump has been written to standard out." > > kill -3 `cat "$CATALINA_PID"` > > Are you certain about this? > > Here is the output of HP-UX: > Thank you for checking! I was just guessing. (I remember users reporting similar problem with wrong value in pid file in some old version of catalina.sh, ~4 years ago.) Apparently this means that this version of nohup is implemented as replacing the old process with a new one, preserving the pid. A feature of unix exec() function. OK, good. If you are using CATALINA_PID files, can you also check that they contain the expected value of process id? BTW, in POSIX.1-2008/2013 there is a recommendation to redirect stdin when invoking nohup. See 'RATIONALE' section in http://pubs.opengroup.org/onlinepubs/9699919799/utilities/nohup.html Their example: nohup make </dev/null & BTW, I think it will be better to explicitly unset _NOHUP variable by default. So that it is not carried over from a caller. It is an internal variable used by catalina.sh. unset _NOHUP -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
