Which statements are true regarding the following syslog.conf configuration directive?

Which statements are true regarding the following syslog.conf configuration directive?

*.err;kern.notice;auth.notice /dev/console

(Select THREE correct answers)

Which statements are true regarding the following syslog.conf configuration directive?

*.err;kern.notice;auth.notice /dev/console

(Select THREE correct answers)

A.
Severity crit messages from all facilities will be directed to /dev/console

B.
Severity notice messages from the auth facility will be directed to /dev/console

C.
Severity notice messages from the kern facility will be directed to /dev/console

D.
Severity err messages from the mail facility will be directed /dev/console

E.
Severity notice messages from all facilities will be directed to /dev/console

Explanation:

From the man pages:
The  priority  is  one  of the following keywords, in ascending order: debug, info, notice, warning, warn (same as warning), err, error (same as err), crit, alert, emerg, panic (same as emerg).  The keywords warn, error and panic are deprecated and should not be used anymore.  The priority defines the severity of the message.
The  behavior  of  the  original  BSD syslogd is that all messages of the specified priority and higher are logged according to the given action.
——
if the directive is *.err;kern.=notice;auth.=notice /dev/



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Chris C

Chris C

A is also true.

The syslogger will log messages of that priority or higher, so having “*.err”, not “*.=err” means crit messages will be logged, as priority goes err, crit, alert, emerg.

http://linux.about.com/od/commands/l/blcmdl5_syslogc.htm:

The behavior of the original BSD syslogd is that all messages of the specified priority and higher are logged according to the given action. This syslogd(8) behaves the same, but has some extensions.