Configuring services. QUESTION BOLDED

From the /etc directory, load rsyslog.conf in vi. This is the configuration file for the rsyslogd daemon. Where do all info messages get logged? Where do cron messages get logged?

Add your own entry to log service (daemon) activity:

daemon.* /var/log/daemons

Explain the rule: what do the two parts specify? Save your rsyslog.conf file. From a terminal window, restart the network service. This should trigger rsyslogd to create the daemons file and store information about the network service. Why didnt it? Even though we changed the rsyslog.conf file, we did not restart the rsyslogd service. Only when a service starts (or restarts) will it read its configuration file. Enter the command to restart rsyslogd. What command did you enter? Restart the network service. Does the file /var/log/daemons now exist? How many lines are in this file?

The rule logs all priority levels which could generate a lot of messages. Lets alter this. Return to the rsyslog.conf file and change daemon.* to daemon.warn, save and exit the file. Delete /var/log/daemons. Restart both the rsyslog service and the network service in that order. Now examine the /var/log/daemons file. It should be empty. Why did nothing get logged? Stop the network service. Start (or restart if it is already running) the ntpd service. This service requires the network service so it should fail. You will see no error message. Look in /var/log/daemons now, how many messages are there? What service is reporting these messages? Change the daemon line to again be daemon.*. Save the file, restart rsyslogd, and start the network service.