<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 22, 2011, at 12:00 PM, Devin Reade wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>SuSE (and perhaps some other distributions) have for a few years<br>been using that BEGIN/END INIT INFO block instead of the 'chkconfig'<br>line to determine ordering, and will do exactly as you described.<br><br>Without having looked into the CentOS 6 case, I would guess that<br>the mechanism used in RHEL has changed to match. This could very<br>well be related to the LSB project, although that's just a guess, too.<br><br>Devin<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>Hi Devin,</div><div><br></div><div>Is it possible to sticky a service then to always start at the value chkconfig lists? Moving various services around like that isn't very helpful when I specifically need services to start is an exact order.</div><div><br></div><div>Or if I do remove the BEGIN/END INIT INFO block from the init scripts will that cause issues?? What's the solution in the SuSE world when someone wants a service to not get reordered??</div><div><br></div><div>Thanks!</div><div><br></div><div>--Jerry</div></body></html>