|
|
This section describes the files in the /var directories, which contain information that varies from machine to machine.
This file contains information about lp(1) scheduling.
This file contains the process ids of the ftp servers running on the system.
This file contains information about users' last login times. See finger(1tcp), fingerd(1Mtcp), and login(1) for more information.
After five unsuccessful login attempts, all the attempts are logged in this file. This file contains one record for each failed attempt.
This file is a registration file for kernel metrics. It is created during system boot and is used by (3mas) library routines, and by sar(1M) and rtpm(1M).
This file contains information about lp(1) shutdowns.
If the SPELL Utilities are installed, this file contains a history of all words that the spell(1) command fails to match. Periodically, review this file for words that you can add to the dictionary. Clear the spellhist file after reviewing it. See spell(1) for information on adding words to the dictionary, cleaning up the spellhist file, and other commands that can be used with the SPELL Utilities.
This file contains a history of
su(1M)
command usage.
As a security measure, this file should not be readable by
others.
Truncate the /var/adm/sulog file periodically
to keep the size of the file within a reasonable limit.
The /usr/sbin/cron, the /sbin/rc0, or the
/sbin/rc2 command can be used to clean up the
sulog file.
You can add the appropriate commands to the
/var/spool/cron/crontabs/root file or add shell commands
to directories such as /etc/rc2.d, /etc/rc3.d,
and so on.
The following two line script truncates the log file
and saves only its last 100 lines:
tail -100 /var/adm/sulog > /var/tmp/sulog
mv /var/tmp/sulog /var/adm/sulog
This file is the SCOadmin event log file.
This file is created by ttymap(1M) at system boot and contains a fast, searchable view of /dev. It is used by ttyname(3C) for optimization purposes.
This file contains information on the current system state. This information is accessed with the who(1) command.
This file contains information similar to that in the /var/adm/utmp file, along with a record of the remote host.
This file contains a history of system logins.
The owner and group of this file must be adm,
and the access permissions must be 664.
Each time
login(1)
is run this file is updated.
As the system is accessed, this file increases in size.
Periodically clear or truncate this file.
The command >/var/adm/wtmp, when executed by root
creates the file with nothing in it.
The following two line script limits the size of
/var/adm/wtmp to the last 3600 characters in the file:
tail -3600c /var/adm/wtmp > /var/tmp/wtmp
mv /var/tmp/wtmp /var/adm/wtmp
The /usr/sbin/cron, /sbin/rc0, or /sbin/rc2 command can be used to clean up the wtmp file. You can add the appropriate commands to the /var/spool/cron/crontabs/root file or add shell commands to directories such as /etc/rc2.d, /etc/rc3.d, and so on.
This file contains information similar to that in the /var/adm/wtmp file, along with a record of the remote host.
This file contains debugging output of the cs(1Mbnu) connection server.
This file logs connection server connections.
This file contains console messages.
This file contains a history of all actions taken by /usr/sbin/cron. Truncate the /var/cron/log file periodically to keep the size of the file within a reasonable limit. The /usr/sbin/cron, /sbin/rc0, or /sbin/rc2 command can be used to clean up the /var/cron/log file. You can add the appropriate commands to the /var/spool/cron/crontabs/root file or add shell commands in the following directories (as applicable): /etc/rc2.d, /etc/rc3.d, and so on.
The following two line script
limits the size of the log file
to the last 100 lines in the file:
tail -100 /var/cron/log > /var/tmp/log
mv /var/tmp/log /var/cron/log