Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 666776

Summary: Chkconfig start order of service "sshd" is too large (/etc/init.d/sshd)
Product: Red Hat Enterprise Linux 5 Reporter: Zhang Huangbin <michaelbibby>
Component: opensshAssignee: Jan F. Chadima <jchadima>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: low    
Version: 5.5CC: pvrabec
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-19 06:29:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zhang Huangbin 2011-01-03 05:53:47 UTC 
Chkconfig start order of service "sshd" is too large (/etc/init.d/sshd).

Unclearly power off might cause damage to OpenLDAP database, it will hangs while system startup. Similiar issue will cause system hangs, it's better to decrease chkconfig start order of service "sshd", so that admin can always log into server for maintaince.

# grep 'chkconfig' /etc/init.d/sshd
# chkconfig: 2345 55 25

Start order '55' is too large, it should be just large than order of "network", "syslog", etc.
Comment 1 Jan F. Chadima 2011-07-11 09:24:12 UTC 
please contact the RH support at http://www.redhat.com/support/