NEWSYSLOG NEWS -- history of user-visible changes. This file: Copyright (C) Planix, Inc. - see COPYING for details Please send bug reports to bugs@robohack.planix.com * User-visible changes since newsyslog-1.1. - add "-s" (don't send signals) for compatability with the native NetBSD version. - note that '-m' and '-M' are deprecated and will be removed in the next major release - added the "/" flag to cause archiving into a ".old" sub-directory. - fixed a bug that prevented non-existant logs from being created by default - fixed a bug that caused unnecessary roll-over when creating a missing log file - fixed a bug that was causing the size to be ignored whenever a time-of-day specification was given as the interval - improved the interaction of '-v' and '-n' so that the mixed output on stdout can be directly processed by a shell (verbose output now appears as a shell comment) - fixed a bug that made very large log files impossible to find and roll over when using size as the only criteria (verbose output said simply "does not exist") - improved backward compatability for some *BSD newsyslog.conf files. - add '-q' (for quiet) option. - add special '-U' option, for NetBSD system build support. - fixed another bug that was causing missing log files to not be created even when '-F' was used. - trimtime day-of-the-month numbers (Mxx) that are larger than the number of days for the current month now only generate a warning and are treated as the number of days in the current month (but maybe it should warn about any number greater than 28 all the time?). * User-visible changes since newsyslog-1.0.103. - finally found and fixed a long-standing (since 1.0.93) locking bug that allowed multiple instances to run with the same config file at the same time. - fixed portability issues with PID value sanity checks on GNU/Linux. - signal names (and their descriptions) are now printed instead of just their numeric values whenever a child process (log compressor) has been killed by a signal. - implemented a more portable signal name translation scheme (all GNU/Linux systems suffered a bug that would cause any signals above #6 to be sent with one added to their values (e.g. SIGUSR1, which is 10 is sent as 11, which ends up as SIGSEGV, which is bad) * User-visible changes since newsyslog-1.0.102. - a new debugging (-d) option allows various levels of verbose internals debugging without performing any actions and is now separate from normal verbose operation (-v) and separate from script generation (-n) - verbose explanitory and debug messages are prefixed with "[-=]*> " to make them clearly visible and separate from script commands. - new log files are created with unique temporary names and then renamed to their proper names only if their permissions and ownership are successfully initialised. (Make sure you use the 'D' flag if the daemon will create its own log files on demand.) - interval trim-time parsing errors are always printed to stderr, not just when '-v' is given. Keep an eye out for e-mail from cron! ;-) * User-visible changes since newsyslog-1.0.101. - run intervals can be one minute (but not less) again. - minor portability fixes for Solaris and linux. * User-visible changes since newsyslog-1.0.100. - a bug in parsing timespecs with "interval-trimtime" that caused strange errors on some machines has been fixed. - signals are displayed symbolically in error messages. - run intervals (-i) of one minute (or less) are no longer allowed. - verbose output shows the trim time in local time (in ISO-8601 format) now instead of as a Unix epoch time. - the rest of the changes are just portability fixes (more Solaris and Linux portability) (though esp. including use of str2sig() for portable signal name translation on SunOS-5). * User-visible changes since newsyslog-1.0.99. - just portability fixes (tested on Solaris-2.6 now) * User-visible changes since newsyslog-1.0.98. - fixed logic bug in comparison of PID filename with /dev/null. - fixed logic bug in setting of internal flag for trim-time specs. - a new test parameter, '-T timenow' has been added to make testing of trim-time specifications easier to do in a timely fashion. * User-visible changes since newsyslog-1.0.97. - the log roll-over interval may now be specified as a "trim time", either as an hour of the day, day of the week, or day of the month, and the latter two may also specify the hour of the day, but default to midnight. - new command-line option '-i' to specify the interval at which newsyslog is called by cron so that it can figure out whether or not a "trim time" specification matches the current time closley enough. - processing can be restricted to specific log files by specifying their names on the command line -- the control information is still taken from the default or specified configuration file. - signalling for "binary" log files now works. - new flag 'D' will prevent log file from being created. - we don't look for a timestamp in the first record if there's no interval specified, which will prevent complaints about unparsable timestamps in files that will never have parsable timestamps. - the configuration file is locked (with open(O_EXLOCK), aka flock(2)) to prevent simultaneous executions from fouling each other up. * User-visible changes since newsyslog-1.0.96. - improved error messages by including line numbers. - new optional "sigtype" field (ala NetBSD). - POSIX demands that user and group values for chmod be separated by colons (since `.' *could* be legal in a user-name), so now the optional second field must similarly be separated into user and group sub-fields with a colon (`:'). - various bug fixes. * User-visible changes since newsyslog-1.0.95. - just bug fixes. * User-visible changes since newsyslog-1.0.94. - just bug fixes. * User-visible changes since newsyslog-1.0.93. - improved usefulness of '-n'. It now output strictly a shell script that would mimic actions without '-n'. All extra information is only output with '-v' now. - bug fixes. * User-visible changes since newsyslog-1.0.92. - added '-p syslogd_pidfile' option (as in FreeBSD) - lots of internal cleanups, logic fixes, portability fixes, etc. * User-visible changes since newsyslog-1.0.91. - added '-F' (force) flag as in FreeBSD's latest version (rev.1.16) - native BSD builds are supported without requiring ./configure. - PID file can be /dev/null to avoid notifying any daemon. - the '0' flag actually works (instead of just showing that it would work in verbose mode). - a better attempt is made to determine the age of the log file when no log.0* file exists (by attempting to parse the timestamp from the first record of the current log file). (WARNING: Some (all?) versions of NetBSD have a buggy strptime(3) library routine that will make this less accurate. PR# lib/5161 contains a patch.) * User-visible changes since newsyslog-1.0.90. - none * User-visible changes since newsyslog-0.1.91. - added '0' flag to leave logfile.0 uncompressed. * User-visible changes since newsyslog-0.1.80. - don't add status message to new log file in order to ensure that stagnant log files stay unchanged (i.e. the "empty" check prevents them from being rolled over unnecessarily). * User-visible changes since NetBSD-1.3.3. - added -M|-m option - separated out newsyslog.conf.5 manual page - improved documentation #ident "@(#)newsyslog:newsyslog-1_1_0_81:NEWS,v 1.29 2009/07/16 00:33:18 woods Exp"