[CentOS] CentOS 6.0 chkconfig strange behavior

2011-07-22 Thread Jerry Moore
Hi, I'm noticing some strangeness with chkconfig on CentOS 6.0 and was looking for a bit of advice. It appears that chkconfig is re sequencing or re ordering the start priority of various services when turning on a service using chkconfig. Example is the network service. Under normal

Re: [CentOS] CentOS 6.0 chkconfig strange behavior

2011-07-22 Thread Jerry Moore
On Jul 22, 2011, at 12:00 PM, Devin Reade wrote: SuSE (and perhaps some other distributions) have for a few years been using that BEGIN/END INIT INFO block instead of the 'chkconfig' line to determine ordering, and will do exactly as you described. Without having looked into the CentOS 6

Re: [CentOS] CentOS 6.0 chkconfig strange behavior

2011-07-22 Thread Jerry Moore
On Jul 22, 2011, at 12:17 PM, Cal Webster wrote: System V init has been replaced by upstart Upstream Deployment Guide: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Technical_Notes/deployment.html Fedora Wiki: http://fedoraproject.org/wiki/Features/Upstart Run

Re: [CentOS] CentOS 6.0 chkconfig strange behavior

2011-07-22 Thread Jerry Moore
On Jul 22, 2011, at 12:10 PM, Devin Reade wrote: Again just guessing (my one test CentOS 6 system doesn't currently have snmpd installed) have a look at not only the snmpd script but also the ones that should have been started between network and snmpd. It sounds like some dependencies are