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 a
On Fri, 2011-07-22 at 12:47 -0700, Jerry Moore wrote:
>
> 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
> >
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
>
--On Friday, July 22, 2011 12:12:28 PM -0700 Jerry Moore
wrote:
> 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.
>
> Or if I do remo
On Fri, 2011-07-22 at 13:00 -0600, Devin Reade wrote:
> --On Friday, July 22, 2011 11:10:29 AM -0700 Jerry Moore
> wrote:
>
> > It appears that chkconfig is re sequencing or re ordering the start
> > priority of various services when turning on a service using chkconfig.
> [...]
> > The only solu
--On Friday, July 22, 2011 11:10:29 AM -0700 Jerry Moore
wrote:
> 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 circumstances network is set
> to start at
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 Cent
--On Friday, July 22, 2011 11:10:29 AM -0700 Jerry Moore
wrote:
> It appears that chkconfig is re sequencing or re ordering the start
> priority of various services when turning on a service using chkconfig.
[...]
> The only solution I've found is to remove the entire BEGIN INIT INFO to
> END INI
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 circumstan
9 matches
Mail list logo
