The last thing I want to cover today is the
newsyslog utility. When you originally looked in your
/var/log directory, you may have received a listing of a lot of files that ended in
.1, etc., and some of these files may have also been compressed (they had a
.gz extension). This is a result of the workings of
newsyslog, which we mentioned briefly in the Getting Cron to Do Our Bidding article. Let's take a quick look in this utility's manpage:
newsyslog - maintain system log files to manageable sizes
Newsyslog is a program that should be scheduled to run periodically by cron(8). When it is executed it archives log files if necessary. If a log file is determined to require archiving, newsyslog rearranges the files so that "logfile" is empty, "logfile.0" has the last period's logs in it, "logfile.1" has the next to last period's logs in it, and so on, up to a user-specified number of archived logs. Optionally, the archived logs can be compressed to save space.
In other words, if a logfile becomes too large,
newsyslog will rename it with a
.0 extension, possibly zip it, and create a new file with the original log name. For example:
maillog.1.gzis the oldest maillog file; it has been compressed
maillog.0.gzis the second oldest maillog file; it is also compressed
maillogis the current maillog that is being written to by syslogd
If you continue to read through the manpage for
newsyslog, you'll learn how to tweak its configuration file (
/etc/newsyslog.conf) so you can schedule when files will be renamed and compressed.
If you ever need to view the contents of a log that has already been compressed by
newsyslog, you can use the
zmore utility like so:
If you need to remove old log files to save space, it is safe to delete a log that ends with a either a number or a
/var/logdirectory. If you need to do this often, there is no need to create a cronjob;
newsyslogwill do this automatically. It will keep as many or as few backlogs as you desire and rotate through them when they reach a specified size. I would not recommend deleting the other logs, though, as
syslogdexpects to be able to find the logfiles in the paths that you've specified in
/etc/syslog.conf. So, in the above example, it is safe to delete
maillog.1.gz, but don't delete
If you ever inadvertently delete an original logfile, you can create it using the
cd /var/log rm maillog (oops) touch maillog
This will create an empty maillog file that syslogd can write to.
This should get you started working with logs on your FreeBSD system. In next week's article we'll dig a little deeper and take a look at processes, PIDs, and the
Dru Lavigne is a network and systems administrator, IT instructor, author and international speaker. She has over a decade of experience administering and teaching Netware, Microsoft, Cisco, Checkpoint, SCO, Solaris, Linux, and BSD systems. A prolific author, she pens the popular FreeBSD Basics column for O'Reilly and is author of BSD Hacks and The Best of FreeBSD Basics.
Read more FreeBSD Basics columns.
Discuss this article in the Operating Systems Forum.
Return to the BSD DevCenter.