Difference between revisions of "Init.d"
From Tassadar
| Line 2: | Line 2: | ||
| − | ''/etc/init.d/bind9 start | + | ''/etc/init.d/bind9 start'' |
| − | /etc/init.d/bind9 stop | + | |
| − | /etc/init.d/bind9 reload | + | ''/etc/init.d/bind9 stop'' |
| − | /etc/init.d/bind9 restart | + | |
| − | '' | + | ''/etc/init.d/bind9 reload'' |
| + | |||
| + | ''/etc/init.d/bind9 restart'' | ||
| + | |||
Reload actually tells BIND to reload its config files, rather than actually restarting. | Reload actually tells BIND to reload its config files, rather than actually restarting. | ||
Latest revision as of 11:28, 30 October 2011
The Windows analog to init.d is the Services MMC. In /etc/init.d, you can find scripts that start, stop, restart, or check the status of running background programs, just like the Services MMC. When you install a program, it usually drops the script into init.d, leaving everything in a convenient place. Typically the script is the name of the program. As an example, /etc/init.d/bind9 is the BIND script. You then throw a command at that script, like the following:
/etc/init.d/bind9 start
/etc/init.d/bind9 stop
/etc/init.d/bind9 reload
/etc/init.d/bind9 restart
Reload actually tells BIND to reload its config files, rather than actually restarting.
