如何正确地将自定义守护进程添加到 init.d?

如何正确地将自定义守护进程添加到 init.d?

我有一个第三方专有应用服务器守护进程,可以通过几行命令行启动和停止。我需要这个守护进程在系统启动时启动,并在系统关闭时正确停止。我该如何正确实现这一点?复制 /etc/init.d 中的一些脚本并进行相应修改就足够了吗?

答案1

init.d 是旧的、已弃用的守护进程启动系统;已被取代暴发户。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

在这种情况下,您可以复制该文件并进行修改。更复杂的配置最好在 upstart 站点和 /etc/init 中的其他条目中记录。

添加以回应评论

无论你使用 upstart 还是 init.d,你仍然需要某种方式来确定 Firebird 何时正确初始化。不幸的是,Firebird 本身似乎没有很好的方法来验证这一点它已安装并正在运行。因此,将程序启动放入 /etc/rc.local 的建议无疑是最简单的,并且在 Ubuntu 上 - 至少 - 可以保证在启动过程中尽可能晚地运行。

答案2

如果您不想迁移到 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 亚马逊云 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

:

答案3

复制 /etc/init.d/skeleton 并在适当的位置编辑它以启动/停止/重新启动您的服务。它注释得很好,因此您应该能够立即创建一个有效的 init.d 脚本。

答案4

2020 年 4 月

这里有一些不错的答案。有关最新说明:

  1. init.d服务被替换为upstart(使用/etc/init而不是/etc/init.d
  2. upstart存在的时间很短,被取代了systemd

创建 systemd 服务

假设您决定命名您的服务myservice,请创建一个文件/etc/systemd/system/myservice.service

[Unit]
Description=A service that I made

[Service]
Type=simple
ExecStart=/bin/bash /home/myuser/myservice.sh

[Install]
WantedBy=multi-user.target

3 个有用的命令:

  1. sudo systemctl enable myservice使服务始终在系统启动时启动
  2. sudo systemctl start myservice手动启动服务
  3. sudo systemctl stop myservice手动停止服务

有关可以放入服务文件中的其他配置选项和合法值,请参阅https://www.freedesktop.org/software/systemd/man/systemd.service.html#Options

相关内容