Question

We are going to configure our system to log messages associated with the mail system. View the letc/rsyslog.conf file to get a sense of how this configuration file works. Create a file called letc/rsyslog.d/local2.conf (to set logging rules) and append the following lines to the end this file: # # LAB 4 steps # local2.* Ivar/log/local2.log (Note: This entry will direct the Linux kernel to log any event relating to the local facility (e-mail) with all severity levels to be saved to a file Called: /var/log/local2.log) C. Since you changed the setup, you must restart the logging service so it recognizes the changes. Give your command that will complete the restart: Issue the following Linux command to test out the system logging setup: logger-p local.info "Testing message" View the content of the /var/log/local2.log file. You should see a message. d. Take a screenshot of the system message in the Ivar/log/local2.log file and paste it here e. Use 'logger' to send an 'informational message to the authentication messages log in '/var/log' that says "Hello Sheridan Linux Users!". Tag the message with the word 'demo'. Give your command here: f. Give a screenshot showing this message in its file:

please post the answer for this question within half an hour and also provide the screenshots for every question including the commands also.

Answer 1

SOLUTION

The following solutions have been implemented in Ubuntu Linux.

The “rsyslog.conf” file contains the configuration settings or rules pertaining to logging of system messages.

Create a new file “/etc/rsyslog.d/local2.conf” and append the configuration lines using the “vim” editor given below

vim /etc/rsyslog.d/local2.conf

The lines are

#

# LAB 4 Steps

#

local2.* /var/log/local2.log

These lines specify all messages associated with local2 facility regardless of priority should be entered in the corresponding log file.

The contents of the file can be viewed using the following command

cat /etc/rsyslog.d/local2.conf

Question C: Restart the logging service and send the following message

Issue the following command to restart the logging service

service rsyslog restart

The command given below can be used to send an informational message to the local2 facility.

logger -p local2.info “Testing message”

The “-p” stands for priority and then parameter given basically of the format “facility.level”.

The actual message is enclosed within “………..“ and given in the end.

Following the execution of the above command, the message will be entered in the /var/log/local2.log file which can be viewed using the following command.

cat /var/log/local2.log

Terminal Window Screenshot

Activities » Terminal - Aug 1 19:01 + root@ubuntu: - a a root@ubuntu:~# vim /etc/rsyslog.d/local2.conf root@ubuntu:~# cat /etc/rsyslog.d/local2.conf # # LAB 4 steps local2.* /var/log/local2.log root@ubuntu:~# service rsyslog restart root@ubuntu:--# logger -p localz.info "Testing message" root@ubuntu:~# root@ubuntu:~# root@ubuntu:-# cat /var/log/local2.log Aug 1 19:00:02 ubuntu arun: Testing message root@ubuntu:-# root@ubuntu:~# 2

Question D: Screenshot of the “/var/log/local2.log” with the entry generated from the previous command execution.

Activities Text Editor - Aug 1 19:04 localz.log [Read-Only] /var/log arun: Testing message Open 1 Aug Save 1 19:00:02 ubuntu A

Question E: Using “logger” send an informational message to the “authentication message log” with the sampe message and “tag” provided.

The following logger message can be used to implement the sending of informational message to the “/var/log/auth.log” file.

logger -p auth.info -t demo "Hello Sheridan Linux Users!"

The “-p” stands for priority and then parameter given basically of the format “facility.level”.

The “-t” stands for “tag”. By default, it takes the username.

The contents of the “auth.log” file after the execution of the above command can be viewed using the command

tail -5 /var/log/auth.log

It displays the last 5 lines(entries) in the corresponding file.

Terminal Window Screenshot

Activities Terminal Aug 1 19:19 SU: + root@ubuntu: root@ubuntu:-# logger -p auth.info -t demo "Hello Sheridan Linux Users! root@ubuntu:-# root@ubuntu:~# root@ubuntu:~# root@ubuntu:-# tail -5 /var/log/auth.log Aug 1 19:11:12 ubuntu (to root) arun on pts/1 Aug 1 19:11:12 ubuntu SU: pam_unix(su: session) : session opened for user root y (uid=1000) Aug 1 19:17:02 ubuntu CRON[5194]: pam_unix(cron: session) : session opened for ser root by (uid=0) Aug 19:17:02 ubuntu CRON[5194]: pam_unix(cron: session): session closed for ser root Aug 1 19:18:07 ubuntu demo: Hello Sheridan Linux Users! root@ubuntu:-# b O U 1 U

Question F: Screenshot of the “auth.log” with the entry generated from the previous command execution.

o . ++ Activities Text Editor Aug 1 19:21 auth.log [Read-Only] Open Save = /var/log securetty: No such file ог directory 244 Aug 1 18:58:32 ubuntu sudo: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=o tty=/dev/pts/1 ruser=arun chost= user=arun 245 Aug 1 18:58:35 ubuntu sudo: pam_unix(sudo:auth): couldn't open /etc/- securetty: No such file or directory 246 Aug1 18:58:54 ubuntu sudo: message repeated 3 times: [ pam_unix(sudo: auth): Couldn't open /etc/securetty: No such file or directory] 247 Aug 1 18:58:54 ubuntu sudo: arun TTY=pts/1 PWD=/home/arun/- Desktop 3 USER=root COMMAND=/usr/sbin/service rsyslog restart 248 Aug 1 18:58:54 ubuntu sudo: pam_unix (sudo: session) : session opened for User root by (uid=O) 249 Aug 1 18:58:54 ubuntu sudo: pam_unix(sudo: session) : session closed for User root 250 Aug 1 19:11:10 ubuntu SU: pam_unix(su:auth): couldn't open /etc/- securetty: No such file or directory 251 Aug 1 19:11:12 ubuntu SU: pam_unix(su:auth): couldn't open /etc/- securetty: No such file ог directory 252 Aug 1 19:11:12 ubuntu SU: (to root) arun on pts/1 253 Aug 1 19:11:12 ubuntu SU: pam_unix(su: session>: session opened for User root by (uid=1000) 254 Aug 1 19:17:02 ubuntu CRON[ 5194]: pam_unix(cron: session) : session opened for User root by (uid=O) 255 Aug 1 19:17:02 ubuntu CRON[5194]: pam_unix(cron: session) : session closed for user coat 256 Aug 1 19:18:07 ubuntu demo: Hello Sheridan Linux Users! 257 Aug 1 19:19:21 ubuntu SU: pam_unixSU: session: session closed for User root A ?

NOTE:

The area highlighted in red is the entry generated corresponding to the “logger” command execution.

Hope this helps.