opendev
/
puppet-log_processor
Code Issues Proposed changes

Start processes after network and named 

Log processing requires networking and name resolution to be available.
Specify these deps in the LSB init headers so that we get proper boot
time start sequences for these services.

Change-Id: Ic36eba2654e7425f3aba8ee5c215150b7d94d658
This commit is contained in:
Clark Boylan 2015-03-04 08:35:54 -08:00
parent d57ecaddbd
commit e3641f727f
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
files/jenkins-log-client.init
View File

@ -1,8 +1,8 @@
#! /bin/sh
### BEGIN INIT INFO
# Provides: jenkins-log-client
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Required-Start: $remote_fs $syslog $named $network
# Required-Stop: $remote_fs $syslog $named $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Jenkins Log Client

4
templates/jenkins-log-worker.init.erb
View File

@ -1,8 +1,8 @@
#! /bin/sh
### BEGIN INIT INFO
# Provides: jenkins-log-worker
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Required-Start: $remote_fs $syslog $named $network
# Required-Stop: $remote_fs $syslog $named $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Jenkins Log Worker