Robert P. J. Day wrote:
Remember, with most services, you have to restart them after making changes in their configuration file(s) before the change will take affect. Just editing a file is not enough.
yes, but there's a trick -- some services support both the "restart" and "reload" actions, as in:
# service fubard restart # service fubard reload
the first would do an actual service restart, while the second would simply tell the service to reconsult its config file -- useful if this is a service you really don't want to stop, even for a second.
but i know you knew that already. :-)
rday
This is true. And it is a lot easier then sending a SIGHUP to the daemon. (I give much better answers after having my first cup of coffee!)
You can get a list of the supported commands by using an invalid option. I like "service <name> help" as in:
# service smb help Usage: /etc/init.d/smb {start|stop|restart|reload|status|condrestart}
Now, one option of the service command I bet most people do not know about is the status-all option. (service --status-all)
service --status-all runs all init scripts, in alphabetical order, with the status command.
But not all scripts support the status option...
Mikkel