如何为程序设置 init.d 脚本?
我在我的服务器上安装了一个名为 node.js 的程序来监听端口 8088
我的服务器是来自 hostgator 的 VPS 软件包级别 3。
现在我尝试创建一个 init.d 脚本,以便 node.js 随系统自动运行,并且在自动崩溃时可以重新启动。
经过一番谷歌搜索后,我发现了一些资源并混合了一个 init.d 脚本。正如你所看到的,它更像是一个复制粘贴工作:)我遇到了一些问题,其中很可能包括 init.d 脚本的 sysntax 错误。
#! /bin/sh
#
# Copyright (c) 2011 Anjan Bhowmik
# All rights reserved.
# Author: Anjan Bhowmik, 2011
#
# /etc/init.d/nodejs
# and its symbolic link
# /usr/sbin/rcnodejs
### BEGIN INIT INFO
# Provides: nodejs
# Required-Start: $network
# Required-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: Node.js daemon
# Description: NOde.js server that listens to port 8088
### END INIT INFO
$NODEJS_BIN = $(which node)
$NODEJS_JS_FILE = /home/anjan/server.js
# Load the rc.status script for this service.
. /etc/rc.status
# Reset status of this service
rc_reset
case "$1" in
start)
echo -n "Starting node.js "
## Start daemon with startproc(8). If this fails
## the return value is set appropriately by startproc.
startproc $NODEJS_BIN $NODEJS_JS_FILE
# Remember status and be verbose
rc_status -v
;;
stop)
echo -n "Shutting down node.js "
## Stop daemon with killproc(8) and if this fails
## killproc sets the return value according to LSB.
killproc -TERM $NODEJS_BIN
# Remember status and be verbose
rc_status -v
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start
# Remember status and be quiet
rc_status
;;
reload)
# If it supports signaling:
echo -n "Reload service node.js "
killproc -HUP $NODEJS_BIN
#touch /var/run/BAR.pid
rc_status -v
## Otherwise if it does not support reload:
#rc_failed 3
#rc_status -v
;;
status)
echo -n "Checking for service node.js "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.
# Return value is slightly different for the status command:
# 0 - service up and running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running (unused)
# 4 - service status unknown :-(
# 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)
# NOTE: checkproc returns LSB compliant status values.
checkproc $NODEJS_BIN
# NOTE: rc_status knows that we called this init script with
# "status" option and adapts its messages accordingly.
rc_status -v
;;
*)
## If no parameters are given, print which are avaiable.
echo "Usage: $0 {start|stop|status|restart|reload}"
exit 1
;;
esac
rc_exit
由于不同的系统使用不同的方法,我真的很困惑。我本地的 ubuntu 使用名为 upstart 的东西,但我的服务器似乎没有 upstart,仅使用 init.d 脚本。
如果我发出“uname -a”,我会得到以下信息:
Linux onl.onlyfreelancer.com 2.6.18-028stab070.14 #1 SMP
Thu Nov 18 16:04:02 MSK 2010 x86_64 x86_64 x86_64 GNU/Linux
此外,我似乎找不到像“insserv”这样的实用程序来启用此 init.d 脚本。那么,如果我的 init.s 脚本是正确的,我该如何正确设置它呢?
非常感谢您的帮助,我已经与这件事斗争了 2 天,但还没有运气。
I have installed a program called node.js on my server to listen on port 8088
My server is a VPS package level 3 from hostgator.
Now i m trying to create a init.d script so that node.js runs automatically with system and can restart if crashed autimatically.
After a bit googling on it, i came across some resources and mashed up a init.d script. Its more of a copy pasting job as u can see :) I got quite some problem, which most probably includes the init.d script having wrong sysntax.
#! /bin/sh
#
# Copyright (c) 2011 Anjan Bhowmik
# All rights reserved.
# Author: Anjan Bhowmik, 2011
#
# /etc/init.d/nodejs
# and its symbolic link
# /usr/sbin/rcnodejs
### BEGIN INIT INFO
# Provides: nodejs
# Required-Start: $network
# Required-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: Node.js daemon
# Description: NOde.js server that listens to port 8088
### END INIT INFO
$NODEJS_BIN = $(which node)
$NODEJS_JS_FILE = /home/anjan/server.js
# Load the rc.status script for this service.
. /etc/rc.status
# Reset status of this service
rc_reset
case "$1" in
start)
echo -n "Starting node.js "
## Start daemon with startproc(8). If this fails
## the return value is set appropriately by startproc.
startproc $NODEJS_BIN $NODEJS_JS_FILE
# Remember status and be verbose
rc_status -v
;;
stop)
echo -n "Shutting down node.js "
## Stop daemon with killproc(8) and if this fails
## killproc sets the return value according to LSB.
killproc -TERM $NODEJS_BIN
# Remember status and be verbose
rc_status -v
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start
# Remember status and be quiet
rc_status
;;
reload)
# If it supports signaling:
echo -n "Reload service node.js "
killproc -HUP $NODEJS_BIN
#touch /var/run/BAR.pid
rc_status -v
## Otherwise if it does not support reload:
#rc_failed 3
#rc_status -v
;;
status)
echo -n "Checking for service node.js "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.
# Return value is slightly different for the status command:
# 0 - service up and running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running (unused)
# 4 - service status unknown :-(
# 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)
# NOTE: checkproc returns LSB compliant status values.
checkproc $NODEJS_BIN
# NOTE: rc_status knows that we called this init script with
# "status" option and adapts its messages accordingly.
rc_status -v
;;
*)
## If no parameters are given, print which are avaiable.
echo "Usage: $0 {start|stop|status|restart|reload}"
exit 1
;;
esac
rc_exit
I really get confused as different systems use different approaches. My local ubuntu uses something called upstart, but my server doesn't seem to have upstart and uses init.d scripts only.
If I issue a "uname -a" I get this:
Linux onl.onlyfreelancer.com 2.6.18-028stab070.14 #1 SMP
Thu Nov 18 16:04:02 MSK 2010 x86_64 x86_64 x86_64 GNU/Linux
Also, I can't seem to find utils like "insserv" to enable this init.d script. So, if my init.s script is correct, how can I set it up correctly?
Any help is much appreciated, I've been battling this thing for 2 days with no luck yet.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
对于关键应用程序,您还可以考虑“不启动服务,运行它们”的方法。 supervisord 和 daemontools 可能会有所帮助。
For critical apps you might also consider the "don't start services, run them" approach. supervisord and daemontools might help here.