Update the comments in this file to reflect the recent changes to

newsyslog.

MFC after:	1 week

1 files changed, 10 insertions, 1 deletions

diff --git a/etc/newsyslog.conf b/etc/newsyslog.conf
index 8c8cd22..dd83edc 100644
--- a/etc/newsyslog.conf
+++ b/etc/newsyslog.conf
@@ -1,13 +1,22 @@
 # configuration file for newsyslog
 # $FreeBSD$
 #
+# Entries which do not specify the '/pid_file' field will cause the
+# syslogd process to be signalled when that log file is rotated.  This
+# action is only appropriate for log files which are written to by the
+# syslogd process (ie, files listed in /etc/syslogd.conf).  If there
+# is no process which needs to be signalled when a given log file is
+# rotated, then the entry for that file should include the 'N' flag.
+#
+# The 'flags' field is one or more of the letters: BCGJNUWZ or a '-'.
+#
 # Note: some sites will want to select more restrictive protections than the
 # defaults.  In particular, it may be desirable to switch many of the 644
 # entries to 640 or 600.  For example, some sites will consider the
 # contents of maillog, messages, and lpd-errs to be confidential.  In the
 # future, these defaults may change to more conservative ones.
 #
-# logfilename          [owner:group]    mode count size when [ZJB] [/pid_file] [sig_num]
+# logfilename          [owner:group]    mode count size when  flags [/pid_file] [sig_num]
 /var/log/all.log			600  7	   *	@T00  J
 /var/log/amd.log			644  7	   100	*     J
 /var/log/auth.log			600  7     100  *     J