Installation guide
You can also use the cron daemon to specify that log files be deleted. The
following is an example of a crontab file entry:
51***find /var/adm/syslog.dated -type d -mtime +5 -exec rm -rf ’{}’ \;
This command line causes all directories under /var/adm/syslog.dated
that were modified more than five days ago to be deleted, along with their
contents, every day at 1:05. Refer to the crontab
(1) reference page for
more information.
13.5 Enhanced Core File Naming
By default when a core file is written to a disk, the system saves the file
under the name core. Each subsequent core file overwrites its predecessor
because the file name is identical. By enabling enhanced core file-naming
the system will attempt to create unique names for core files in the form
core.prog-name.host-name.tag. The uniquely named files that result
will not be overwritten by subsequent core files, thereby preventing the loss
of valuable debugging information when the same program or multiple
programs fail multiple times (and perhaps for different reasons).
The enhanced name provides the following identification data:
• core – The literal string core
• program_name – Up to sixteen characters taken from the program
name as shown by the ps command.
• host_name – The first portion of the system’s network host name, or up
to 16 characters of the host name, taken from the part of the host name
that precedes the first dot. For example, the fourth core file generated
on host buggy.net.ooze.com by the program dropsy would be
core.dropsy.buggy.3
• numeric_tag – The tag assigned to the core file to make it unique among
all the core files generated by a program on a host. The maximum value
for this tag, and thus the maximum number of core files for this
program and host, is set by a system configuration parameter.
Note that the tag is not a literal version number. The system selects the
first available unique tag for the core file. For example, if a program’s
core files have tags .0, .1, and .3, the system uses tag .2 for the next
core file it creates for that program. By default, the system can create
up to 16 versions of a core file. If the system-configured limit for core
file instances is reached, the system will not create any more core files
for that program and host combination.
If you plan to save a number of uniquely named core files, be aware that
core files can quickly consume available disk space. Allowing core files to be
saved under different names in a file system with minimal free space can
13–14 Administering Events and Errors