linux中的rc.status文件是什么

我正在创建一个linux服务，在骨架文件中提到，我们需要运行各种rc命令（rc status、rc_reset）来更新服务状态。这实际上意味着什么。我在谷歌上搜索过，但找不到很多细节。有人能帮我吗

您需要一个shell脚本来停止/启动/重新启动您的服务并给出其状态。 这些脚本通常称为rc脚本。在目录/etc/init.d中查看一些示例-/etc/init.d/klogd是一个非常简单的示例

它们位于init.d中的原因是，它们还需要在启动时自动运行以恢复服务

---

每个Linux变体在引导工作方式上都有点不同，但Debian系统是相当典型的，因为它是许多其他发行版的基础-请参见

我认为rc.status中的命令实际上是特定于SuSe的。它们处理两件事：向用户输出和脚本的最终返回状态

rc_status

检查上一个命令（即服务的启动/重新启动/停止）是否成功执行，并设置“状态值”，即

rc_exit

返回的返回值（放在init.d脚本末尾）

---

可以想象，在没有它们的情况下编写shell脚本，但我认为它们有助于确保脚本符合LSB要求，并与其他系统脚本很好地融合。不过，我敢打赌，大部分内容实际上都记录在

/etc/rc.status

文件中。我手头没有suse框。

这是suse Linux Enterprise Server 11 SP3的/etc/init.d/skeleton中的注释块：

#!/bin/sh
#
#     Template SUSE system startup script for example service/daemon FOO
#     Copyright (C) 1995--2005  Kurt Garloff, SUSE / Novell Inc.
#          
#     This library is free software; you can redistribute it and/or modify it
#     under the terms of the GNU Lesser General Public License as published by
#     the Free Software Foundation; either version 2.1 of the License, or (at
#     your option) any later version.
#                 
#     This library is distributed in the hope that it will be useful, but
#     WITHOUT ANY WARRANTY; without even the implied warranty of
#     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
#     Lesser General Public License for more details.
#      
#     You should have received a copy of the GNU Lesser General Public
#     License along with this library; if not, write to the Free Software
#     Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307,
#     USA.
#
# /etc/init.d/FOO
#   and its symbolic link
# /(usr/)sbin/rcFOO
#
# Template system startup script for some example service/daemon FOO
#
# LSB compatible service control script; see http://www.linuxbase.org/spec/
# 
# Note: This template uses functions rc_XXX defined in /etc/rc.status on
# UnitedLinux/SUSE/Novell based Linux distributions. If you want to base your
# script on this template and ensure that it works on non UL based LSB 
# compliant Linux distributions, you either have to provide the rc.status
# functions from UL or change the script to work without them.
# See skeleton.compat for a template that works with other distros as well.
#
### BEGIN INIT INFO
# Provides:          FOO
# Required-Start:    $syslog $remote_fs
# Should-Start:      $time ypbind smtp
# Required-Stop:     $syslog $remote_fs
# Should-Stop:       ypbind smtp
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: FOO XYZ daemon providing ZYX
# Description:       Start FOO to allow XY and provide YZ
#   continued on second line by '#<TAB>'
#   should contain enough info for the runlevel editor
#   to give admin some idea what this service does and
#   what it's needed for ...
#   (The Short-Description should already be a good hint.)
### END INIT INFO
# 
# Any extensions to the keywords given above should be preceeded by 
# X-VendorTag- (X-UnitedLinux- X-SuSE- for us) according to LSB.
# 
# Notes on Required-Start/Should-Start:
# * There are two different issues that are solved by Required-Start
#    and Should-Start
# (a) Hard dependencies: This is used by the runlevel editor to determine
#     which services absolutely need to be started to make the start of
#     this service make sense. Example: nfsserver should have
#     Required-Start: $portmap
#     Also, required services are started before the dependent ones.
#     The runlevel editor will warn about such missing hard dependencies
#     and suggest enabling. During system startup, you may expect an error,
#     if the dependency is not fulfilled.
# (b) Specifying the init script ordering, not real (hard) dependencies.
#     This is needed by insserv to determine which service should be
#     started first (and at a later stage what services can be started
#     in parallel). The tag Should-Start: is used for this.
#     It tells, that if a service is available, it should be started
#     before. If not, never mind.
# * When specifying hard dependencies or ordering requirements, you can 
#   use names of services (contents of their Provides: section)
#   or pseudo names starting with a $. The following ones are available
#   according to LSB (1.1):
#   $local_fs       all local file systems are mounted
#               (most services should need this!)
#   $remote_fs      all remote file systems are mounted
#               (note that /usr may be remote, so
#                many services should Require this!)
#   $syslog         system logging facility up
#   $network        low level networking (eth card, ...)
#   $named          hostname resolution available
#   $netdaemons     all network daemons are running
#   The $netdaemons pseudo service has been removed in LSB 1.2.
#   For now, we still offer it for backward compatibility.
#   These are new (LSB 1.2):
#   $time           the system time has been set correctly  
#   $portmap        SunRPC portmapping service available
#   UnitedLinux extensions:
#   $ALL            indicates that a script should be inserted
#               at the end
# * The services specified in the stop tags 
#   (Required-Stop/Should-Stop)
#   specify which services need to be still running when this service
#   is shut down. Often the entries there are just copies or a subset 
#   from the respective start tag.
# * Should-Start/Stop are now part of LSB as of 2.0,
#   formerly SUSE/Unitedlinux used X-UnitedLinux-Should-Start/-Stop.
#   insserv does support both variants.
# * X-UnitedLinux-Default-Enabled: yes/no is used at installation time
#   (%fillup_and_insserv macro in %post of many RPMs) to specify whether
#   a startup script should default to be enabled after installation.
#   It's not used by insserv.
#
# Note on runlevels:
# 0 - halt/poweroff             6 - reboot
# 1 - single user           2 - multiuser without network exported
# 3 - multiuser w/ network (text mode)  5 - multiuser w/ network and X11 (xdm)
# 
# Note on script names:
# http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/scrptnames.html
# A registry has been set up to manage the init script namespace.
# http://www.lanana.org/
# Please use the names already registered or register one or use a
# vendor prefix.
#...
# Source LSB init functions
# providing start_daemon, killproc, pidofproc, 
# log_success_msg, log_failure_msg and log_warning_msg.
# This is currently not used by UnitedLinux based distributions and
# not needed for init scripts for UnitedLinux only. If it is used,
# the functions from rc.status should not be sourced or used.
#. /lib/lsb/init-functions
#
# Shell functions sourced from /etc/rc.status:
#      rc_check         check and set local and overall rc status
#      rc_status        check and set local and overall rc status
#      rc_status -v     be verbose in local rc status and clear it afterwards
#      rc_status -v -r  ditto and clear both the local and overall rc status
#      rc_status -s     display "skipped" and exit with status 3
#      rc_status -u     display "unused" and exit with status 3
#      rc_failed        set local and overall rc status to failed
#      rc_failed <num>  set local and overall rc status to <num>
#      rc_reset         clear both the local and overall rc status
#      rc_exit          exit appropriate to overall rc status
#      rc_active        checks whether a service is activated by symlinks
#...
#
# Return values acc. to LSB for all commands but status:
# 0   - success
# 1       - generic or unspecified error
# 2       - invalid or excess argument(s)
# 3       - unimplemented feature (e.g. "reload")
# 4       - user had insufficient privileges
# 5       - program is not installed
# 6       - program is not configured
# 7       - program is not running
# 8--199  - reserved (8--99 LSB, 100--149 distrib, 150--199 appl)
# 
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signaling is not supported) are
# considered a success.
#...
## 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.)

# /etc/rc.status
# vim: syntax=sh
# Definition of boot script return messages
#
#   The bootscripts should use the variables rc_done and rc_failed to
#   report whether they failed or succeeded.  See /etc/init.d/skeleton for
#   an example how the shell functions rc_status and rc_reset are used.
#
#   These functions make use of the variables rc_done and rc_failed;
#   rc_done_up and rc_failed_up are the same as rc_done and rc_failed
#   but contain a terminal code to move up one line before the output
#   of the actual string. (This is particularly useful when the script
#    starts a daemon which produces user output with a newline character)
#
#   The variable rc_reset is used by the master resource control script
#   /etc/init.d/rc to turn off all attributes and switch to the standard
#   character set.
#
#    \033          ascii ESCape
#    \033[<NUM>G   move to column <NUM> (linux console, xterm, not vt100)
#    \033[<NUM>C   move <NUM> columns forward but only upto last column
#    \033[<NUM>D   move <NUM> columns backward but only upto first column
#    \033[<NUM>A   move <NUM> rows up
#    \033[<NUM>B   move <NUM> rows down
#    \033[1m       switch on bold
#    \033[31m      switch on red
#    \033[32m      switch on green
#    \033[33m      switch on yellow
#    \033[m        switch off color/bold
#    \017          exit alternate mode (xterm, vt100, linux console)
#    \033[10m      exit alternate mode (linux console)
#    \015          carriage return (without newline)

#/垃圾箱/垃圾箱
#
#模板SUSE系统启动脚本，例如服务/守护程序FOO
#版权所有（C）1995年-2005年Kurt Garloff，SUSE/Novell公司。
#          
#这个图书馆是免费软件；您可以重新分发和/或修改它
#根据由发布的GNU Lesser通用公共许可证的条款
自由软件基金会；许可证的2.1版，或
#您的选择）任何更高版本。
#                 
#这个图书馆的发行是希望它有用，但是
#无任何保证；甚至没有任何关于
#适销性或适合某一特定目的。见GNU
#有关更多详细信息，请参阅较低的通用公共许可证。
#      
#您应该已经收到GNU Lesser General Public的副本
#与此库一起使用的许可证；如果没有，请写信给自由软件
基金会，59寺庙广场，套房330，波士顿，MA 02111-1307，
#美国。
#
#/etc/init.d/FOO
#以及它的象征性联系
#/（usr/）sbin/rcFOO
#
#某些示例服务/守护程序FOO的模板系统启动脚本
#
#与LSB兼容的服务控制脚本；看见http://www.linuxbase.org/spec/
# 
#注意：此模板使用/etc/rc.status on中定义的函数rc_XXX
#基于UnitedLinux/SUSE/Novell的Linux发行版。如果你想建立你的
#在此模板上编写脚本，并确保它在非基于UL的LSB上工作
#兼容Linux发行版，您必须提供rc.status
#函数，或者将脚本更改为在没有它们的情况下工作。
#请参阅skeleton.compat，以了解可与其他发行版一起使用的模板。
#
###开始初始化信息
#提供：富
#必需的开始：$syslog$remote\u fs
#应该开始：$time-ypbind-smtp
#所需停止：$syslog$remote\u fs
#应停止：ypbind smtp
#默认开始：3 5
#默认停止：0 1 2 6
#简短描述：FOO-XYZ守护进程提供ZYX
#说明：启动FOO以允许XY并提供YZ
#第二行由“#”继续
#应该包含足够的运行级编辑器信息
#让管理员了解此服务的功能和
#它需要什么。。。
#（简短的描述应该已经是一个很好的提示。）
###结束初始化信息
# 
#对上述关键词的任何扩展都应在
#X-VendorTag-（X-UnitedLinux-X-SuSE-为我们）根据LSB。
# 
#关于所需启动/应启动的注意事项：
#*有两个不同的问题需要通过必要的启动来解决
#应该开始了
#（a）硬依赖项：运行级别编辑器使用它来确定
#哪些服务绝对需要启动才能启动
#这项服务很有意义。示例：nfsserver应该具有
#必需的开始：$portmap
#此外，所需的服务在依赖服务之前启动。
#运行级编辑器将警告此类丢失的硬依赖项
#并建议启用。在系统启动期间，可能会出现错误，
#如果未满足依赖项，则返回。
#（b）指定初始化脚本顺序，而不是实际（硬）依赖项。
#InServ需要这一点来确定应该使用哪个服务
#首先启动（以及在稍后阶段可以启动哪些服务）
#并行）。标记应开始：用于此操作。
#它告诉我们，如果服务可用，就应该启动它
#以前。如果没有，没关系。
#*在指定硬依赖项或订购要求时，您可以
#使用服务名称（其提供的内容：部分）
#或以$开头的伪名称。以下是可用的
#根据LSB（1.1）：
#$local\u fs所有本地文件系统都已装入
#（大多数服务都需要这个！）
#$remote\u fs所有远程文件系统都已装入
#（注意/usr可能是远程的，所以
#许多服务都需要这样做！）
#$syslog系统日志记录功能已启动
#$网络低层网络（eth卡，…）
#$named主机名解析可用
#$NetDaemon所有网络守护程序都在运行
#$netdaemons伪服务已在LSB 1.2中删除。
#目前，我们仍然提供向后兼容性。
#这些是新的（LSB 1.2）：
#$time系统时间已正确设置
#$portmap SunRPC portmap