Tag Info

New answers tagged

0

I've just been going through this issue and created a solution based on Josh's above. It get's around the 'sleep 10' issue by using a chkconfig header that ensures that the script waits for suitable services to be available before attempting to start. Heres my init.d script: #!/bin/bash # # Kibana Init script for Kibana # # chkconfig: 345 99 76 # ...


0

In my configuration (corosync 1.4.2-3) I use the service.d out of corosync. /etc/corosync/service.d/pcmk service { # Load the Pacemaker Cluster Resource Manager name: pacemaker ver: 0 } This tells corosync to start the pacemaker resource manager. You won't have initscripts for pacemaker in this configuration (and even service ...



Top 50 recent answers are included