|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc |
|
| #
3679fd1e |
| 02-Feb-2018 |
zrj <rimvydas.jasinskas@gmail.com> |
newsyslog(8): Add missing fallthrough.
|
| #
2bc1c426 |
| 29-Jan-2018 |
Sascha Wildner <saw@online.de> |
newsyslog(8): Further reduce differences with FreeBSD.
|
| #
e7773cc7 |
| 29-Jan-2018 |
Antonio Huete Jimenez <tuxillo@quantumachine.net> |
newsyslog - Allow writing RFC5424 compliant rotation message.
This modification adds the capability to newsyslog to write the
rotation message in a format that is compliant with RFC5424. This
capabi
newsyslog - Allow writing RFC5424 compliant rotation message.
This modification adds the capability to newsyslog to write the
rotation message in a format that is compliant with RFC5424. This
capability is enabled on a per-log file basis through a new value
("T") in the flags field in newsyslog.conf. This is useful on systems
that use the RFC5424 format for log files so that the rotation message
format matches that of the other log messages. There has been recent
mention of adding an RFC5424 compliant mode to syslogd and at least
one alternative system log daemon (rsyslogd) that already has the
capability to use that format.
Obtained-from: FreeBSD (r318960)
show more ...
|
|
Revision tags: v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
| #
521a7b05 |
| 12-May-2007 |
Sascha Wildner <swildner@dragonflybsd.org> |
Sync newsyslog(8) with FreeBSD's current code.
New things:
* Re-ordering of the rotate/signal steps. First, rotate all files which
need to be rotated and then send a single signal to each daemon
Sync newsyslog(8) with FreeBSD's current code.
New things:
* Re-ordering of the rotate/signal steps. First, rotate all files which
need to be rotated and then send a single signal to each daemon that
needs to be notified. This way, each daemon will only be signaled once
instead of once per file.
* Allow /var/log to be a symbolic link.
* -d option for specifying an alternate root for log files.
* -D option for debugging purposes.
* -N option to suppress log file rotation (intended to be used in
conjunction with -C and -CC).
* Bug fixes and minor improvements.
Note: FreeBSD's r1.107 of newsyslog.c was not brought in as it generates
a warning in DragonFly instead of fixing one.
show more ...
|