https://bugzilla.redhat.com/show_bug.cgi?id=1347864
--- Comment #4 from Coty Sutherland <csutherl(a)redhat.com> ---
Forking is what we actually want to avoid.
For what reason? Simple just fires the script and doesn't care about a return.
Forking is more closely what SysV was doing and actually provides feedback when
the process exits abnormally. The only benefit I see to using simple is that it
kills the process when it doesn't stop in time (forking may also do that, but I
haven't tested).
If it is waiting for TimeoutStopSec or not.
I've already done that. I think the problem is that the tomcat stop call forks
off and does it's thing, which returns immediately and sigterms the process
before it can complete a shutdown. I've tried TimeoutStopSec, TimeoutSec, and I
even tried putting a sleep in the server script after the stop to allow it time
to finish; none of that worked for me :(
Hopefully you will have better luck because I'm stuck, but I'll keep poking
around at it also.
--
You are receiving this mail because:
You are on the CC list for the bug.