[英]puppet service resource, enable, init script order
In puppet, if you enable a service like this:在 puppet 中,如果您启用这样的服务:
service { 'myservice':
ensure => running,
enable => true,
subscribe => File['/etc/init.d/myservice'];
}
file { '/etc/init.d/myservice':
source => "puppet:///modules/myservice/myservice",
ensure => file,
owner => root,
group => root,
mode => '0755',
}
Then puppet creates /etc/rc3.d/S??myservice
and in my case, it always creates S65myservice
.然后 puppet 创建/etc/rc3.d/S??myservice
,就我而言,它总是创建S65myservice
。 Where does the 65 come from? 65从哪里来? If puppet is choosing 65 consistently, it must be determined somewhere, but I don't know how it's making that decision.如果傀儡一直选择 65,它必须在某个地方确定,但我不知道它是如何做出这个决定的。 How do I make this service start later in the boot process?如何在引导过程中稍后启动此服务? (for example S99myservice
) (例如S99myservice
)
The order can be changed by adding a chkconfig clause to the startup script, such as:可以通过在启动脚本中添加 chkconfig 子句来更改顺序,例如:
#!/bin/sh
#
# chkconfig: 35 59 80
The above service should start at run level 3 and 5 using startup order 59, and shutdown order 80.上述服务应使用启动顺序 59 和关闭顺序 80 从运行级别 3 和 5 启动。
http://lpetr.org/blog/archives/startup-order-of-services-on-rhel-or-centos http://lpetr.org/blog/archives/startup-order-of-services-on-rhel-or-centos
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.