🚀 go-pugleaf

��������redhat�Լ��ģ�����������ͦ�����
����chkconfig��man page

RUNLEVEL FILES
       Each  service which should be manageable by chkconfig needs two or
more
       commented lines added to its init.d script. The first line  tells
chk-
       config  what  runlevels the service should be started in by default,
as
       well as the start and stop priority levels. If the service should
not,
       by default, be started in any runlevels, a - should be used in place
of
       the runlevels list.  The second line contains  a  description  for
the
       service,  and may be extended across multiple lines with backslash
con-
       tinuation.

       For example, random.init has these three lines:
       # chkconfig: 2345 20 80
       # description: Saves and restores system entropy pool for \
       #              higher quality random number generation.
       This says that the random script should be started in levels 2,  3,
4,
       and 5, that its start priority should be 20, and that its stop
priority
       should be 80.  You should be able to figure out  what  the
description
       says;  the \ causes the line to be continued.  The extra space in
front
       of the line is ignored.





�����Ǵ�lsb����Ū������



Installation and removal of init.d files
An init.d file is installed by copying it into /etc/init.d (which may be a
symlink to another location). This can be done by the package installer.
During the package's postinstall script, the program
"/usr/lib/lsb/install_initd" configures the distribution's boot script
system to call the package's init.d file at the appropriate time.

The install_initd program takes a single argument, the pathanme to the
/etc/init.d file. For example:

	/usr/lib/lsb/install_initd /etc/init.d/example.com-coffeed

When a software package is removed, the package's preuninstall script shall
call /usr/lib/lsb/remove_initd and pass the pathname to the /etc/init.d
file. The package manager is still responsible for removing the /etc/init.d
file; the remove_initd program is provided in case the distribution needs to
clean up any other modifications in the distribution's boot script system
that might have been made by the install_initd program. For example:

	/usr/lib/lsb/remove_initd /etc/init.d/example.com-coffeed

There should be a tool available to the user (e.g., RedHat's chkconfig)
which can be used by the system administrator to easily manipulate at which
init levels a particular init.d script is started or stopped. This
specification currently does not specify such an interface, however.