PLDWWW: Docs/man/Starting-stopping particular subsystems

[glen]

Author: glen   Date: Mon Oct 20 18:46:11 2008 GMT
Module: PLDWWW   URL: http://www.pld-linux.org/Docs/man/Starting-stopping_particular_subsystems?action=diff&rev2=2&rev1=1
---- Log message:
use service

---- Page affected: Docs/man/Starting-stopping particular subsystems

---- Diffs:

================================================================
The comment on the change is:
use service

  Running of particular subsystems/services can be easily controlled with system scripts. Each vital subsystem/service has its driver script available in /etc/rc.d/init.d/ directory. If you run script without parameters, it displays short info, e.g. network subsystem script displays:
  
  {{{
- # /etc/rc.d/init.d/network
+ # service network
  Usage: /etc/rc.d/init.d/network {start|stop|restart|status}
  }}}	
  
  Most scripts support start, stop, restart, and status argument:
  
- || start || runs the subsystem/service ||
+ || start || starts the subsystem/service ||
  || stop || stops the subsystem/service ||
  || restart || restarts the subsystem/service. Usually this is equivalent to start and stop, but in some cases it can be different. ||
  || status || shows the status of the subsystem/service ||
@@ -21, +21 @@

  This example sequence stops and starts network again (turning on/off existing interfaces, setting default routing, etc. See )
  
  {{{
- [root at pldmachine root]# /etc/rc.d/init.d/network stop
+ [root at pldmachine root]# service network stop
  Shutting down interface eth0.......................................[ DONE ]
  Shutting down interface eth1.......................................[ DONE ]
- [root at pldmachine root]# /etc/rc.d/init.d/network start
+ [root at pldmachine root]# service network start
  Setting network parameters.........................................[ DONE ]
  Bringing up interface eth0.........................................[ DONE ]
  Bringing up interface eth1.........................................[ DONE ]
@@ -35, +35 @@

  Every subsystem script contains information in what runlevels that subsystem should be started by default with line like this (example line from /etc/rc.d/init.d/syslog subsystem):
  
  {{{
- # chkconfig:    2345 30 70>
+ # chkconfig:    2345 30 70
  }}}
  
  This tells rc-scripts to run the subsystem when entering runlevels 2, 3, 4, 5 (and respectively, to stop subsystem when leaving one of these runlevels). Numbers 30 and 70 are priority levels for start/stop. See chkconfig(8) for details.