Red Hat Bugzilla – Bug 204371
innd.init script should use ctlinnd to stop the server
Last modified: 2008-01-07 10:51:34 EST
The recommended method to shut down innd is to use "ctlinnd throttle" followed
by "ctlinnd shutdown". However, the innd.init script doesn't do this; it simply
calls "killproc innd". This is non-optimal.
The attached patch modifies the behavior of innd.init when stopping the server
to first use ctlinnd, then fallback to using killproc if ctlinnd doesn't work
for some reason.
(I was fairly conservative with the timeouts; it probably wouldn't be
unreasonable to shorten them a little bit.)
Created attachment 135072 [details]
patch to make innd.init use ctlinnd to shutdown innd
Applied to CVS...
The following on F-8 appears to be related to this patch.
# service innd start
Starting INND system: Starting innd.
[ OK ]
# service innd stop
Stopping INND service (gently): /etc/init.d/innd: line 56: /ctlinnd: No such
file or directory
Stopping INND service (the hard way): [ OK ]
# rpm -ql inn |grep ctli
# rpm -q inn
Thanks for report and reopening, but it is not related. Problem you see is
related to #401241 and was caused by bad changes by previous maintainer in
initscript review changes - because of them stop() can't see $NEWSBIN directory
and can't execute ctlinnd to gently shutdown innd. Closing RAWHIDE again, please
use #401241 for further discussion about that problem.