如何正确地将自定义守护程序添加到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”更改为真实名称！

将将作为服务运行的程序保存在/usr /sbin sudo cp myprogramname /usr/sbin/myscriptname中
创建一个基本的启动脚本(使用/etc/init.d/skeleton作为参考)
将此脚本移动到/etc/init.d sudo mv /etc/init.d/myscriptname
授予此脚本可执行权限(我使用775，但可以将其设置得较低)sudo chmod 755 /etc/init.d/myscriptname
转到/etc/init.d cd /etc/init.d
具有低启动优先级的启动列表中包含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脚本。

参考资料

How to correctly add a custom daemon to init.d?