當前位置: 首頁>>技術教程>>正文


如何正確地將自定義守護程序添加到init.d?

, , ,

問題描述

我有一個第三方專有應用程序服務器守護程序,可以通過幾個命令行來啟動和停止它。我需要該守護程序在係統啟動時啟動,並在係統關閉時正確停止。我該如何正確實施?在/etc/init.d中複製一些腳本並進行相應修改是否足夠?

最佳答案

init.d是舊的,不讚成使用的啟動守護程序的係統; upstart已取代。 Upstart的優點是易於配置,並且可以對任務初始化進行適當的排序。

upstart的配置文件位於/etc /init中,如果您的守護程序沒有任何先決條件,則可以像tty1.conf一樣簡單:

# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]

respawn
exec /sbin/getty -8 38400 tty1

在這種情況下,您可以複製該文件並修改其口味。最好在新貴網站和/etc /init中的其他條目中記錄更複雜的配置。

添加以回應評論

無論您使用upstart還是init.d,您仍然需要一些方法來確定Firebird何時正確初始化。不幸的是,Firebird本身似乎沒有驗證it is installed and running的好方法。因此,將程序啟動到/etc/rc.local的建議當然是最簡單的,並且至少在Ubuntu上-確保在啟動過程中盡可能晚地運行。

次佳答案

如果您不想遷移到UPSTART,但希望使用經典方法,則必須:

注意:我會將服務和程序以相同的名稱保存在不同的目錄中(但是您可以更改它,隻要它反映在服務文件中即可)。將”myscriptname”和”myprogramname”更改為真實名稱!

  1. 將將作為服務運行的程序保存在/usr /sbin sudo cp myprogramname /usr/sbin/myscriptname

  2. 創建一個基本的啟動腳本(使用/etc/init.d/skeleton作為參考)

  3. 將此腳本移動到/etc/init.d sudo mv /etc/init.d/myscriptname

  4. 授予此腳本可執行權限(我使用775,但可以將其設置得較低)sudo chmod 755 /etc/init.d/myscriptname

  5. 轉到/etc/init.d cd /etc/init.d

  6. 具有低啟動優先級的啟動列表中包含sudo update-rc.d myscriptname defaults 97 03

重新啟動計算機,然後檢查服務是否已正確啟動

sudo ps -A --sort cmd

如果您的服務無法正常啟動,則應首先檢查它是否在手動調用時運行:

cd /etc/init.d
sudo service myscriptname start

在下麵,我提供了一個實際有效的示例服務文件。將其與框架服務進行比較,以了解您需要配置的內容。注意:這適用於Ubuntu 12.04 amazon cloud AWS EC2經典LAMP實現(也適用於Kubuntu 15.10)。

#! /bin/sh
### BEGIN INIT INFO
# Provides:          
# Required-Start:    $remote_fs
# Required-Stop:     $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Sample_GT02 daemon startup script
# Description:       Sample Server for GT02 class 
### END INIT INFO

# Author: Tony Gil 
#

# Do NOT "set -e"

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="Sample Daemon"
NAME=sampleserver_gt02
DAEMON=/usr/sbin/$NAME
PIDFILE=/var/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME
CHUID=root

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service
#
do_start()
{
   # Return
   #   0 if daemon has been started
   #   1 if daemon was already running
   #   2 if daemon could not be started
   start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
      || return 1
   start-stop-daemon --start --quiet --chuid $CHUID --pidfile $PIDFILE --exec $DAEMON -- \
      $DAEMON_ARGS \
      || return 2
}

#
# Function that stops the daemon/service
#
do_stop()
{
   # Return
   #   0 if daemon has been stopped
   #   1 if daemon was already stopped
   #   2 if daemon could not be stopped
   #   other if a failure occurred
   start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
   RETVAL="$?"
   [ "$RETVAL" = 2 ] && return 2
   # Wait for children to finish too if this is a daemon that forks
   # and if the daemon is only ever run from this initscript.
   # If the above conditions are not satisfied then add some other code
   # that waits for the process to drop all resources that could be
   # needed by services started subsequently.  A last resort is to
   # sleep for some time.
   start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
   [ "$?" = 2 ] && return 2
   # Many daemons don't delete their pidfiles when they exit.
   rm -f $PIDFILE
   return "$RETVAL"
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
   #
   # If the daemon can reload its configuration without
   # restarting (for example, when it is sent a SIGHUP),
   # then implement that here.
   #
   start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
   return 0
}

case "$1" in
  start)
   [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
   do_start
   case "$?" in
      0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
      2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
   esac
   ;;
  stop)
   [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
   do_stop
   case "$?" in
      0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
      2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
   esac
   ;;
  #reload|force-reload)
   #
   # If do_reload() is not implemented then leave this commented out
   # and leave 'force-reload' as an alias for 'restart'.
   #
   #log_daemon_msg "Reloading $DESC" "$NAME"
   #do_reload
   #log_end_msg $?
   #;;
  restart|force-reload)
   #
   # If the "reload" option is implemented then remove the
   # 'force-reload' alias
   #
   log_daemon_msg "Restarting $DESC" "$NAME"
   do_stop
   case "$?" in
     0|1)
      do_start
      case "$?" in
         0) log_end_msg 0 ;;
         1) log_end_msg 1 ;; # Old process is still running
         *) log_end_msg 1 ;; # Failed to start
      esac
      ;;
     *)
        # Failed to stop
      log_end_msg 1
      ;;
   esac
   ;;
  *)
   #echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload}" >&2
   echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
   exit 3
   ;;
esac

:

第三種答案

複製/etc/init.d/skeleton並在適當的位置進行編輯以啟動/停止/重新啟動服務。它的評論很好,因此您應該能夠立即創建一個有效的init.d腳本。

參考資料

本文由Ubuntu問答整理, 博文地址: https://ubuntuqa.com/zh-tw/article/8993.html,未經允許,請勿轉載。