You are attempting to troubleshoot an event that should have made an entry into the messages
log. This event happened about two weeks ago. Which file should you look at first?
A.
/var/adm/messages
B.
/var/adm/messages.0
C.
/var /adm/messagas.1
D.
/var/adm/messages.2
E.
/var/adm/messages.3
Explanation:
The /var/adm/messages is the file to which all the messages printed on the console
are logged to by the Operating System. This helps to track back check the console messages totroubleshoot any issues on the system.
Syslog daemon also writes to this /var/adm/messages file.
The /var/adm/messages file monitored and managed by newsyslog and its configuration file is
/usr/lib/newsyslog.
This script runs as the roots cron job everyday, checks the /var/adm/messages file and
copies/moves it to /var/adm/messages.0, 1, 2, 3, 4, 5, 6, 7. In other words, it does the Log
Rotation for the /var/adm/messages.
In an event the /var file system is running out of space, these files needs to checked and can be
removed (not the actual /var/adm/messages itself) to free up space on the file system.
However, care has to be taken, if you decide to empty the /var/adm/messages itself for any
reason. This process is called Truncation.
References: SOLARIS SYSTEM ADMIN TIPS, /var/adm/messages
C
C
man logadm
Two options control when a log file is rotated. They are: -s
size -p period.
When using more than one of these options at a time, there
is an implied and between them. This means that all condi-
tions must be met before the log is rotated.
If neither of these two options are specified, the default
conditions for rotating a log file are: -s 1b -p 1w, which
means the log file is only rotated if the size is non-zero
and if at least 1 week has passed since the last time it was
rotated.
c, because the message save the dates 10 days on that file, two weeks (15 days), because /var/adm/messages (first day), /var/adm/messages.0 (1-10 days) so /var/adm/messages.1 (10-20 days)