#
1d386b48 |
|
16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line .c pattern Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
#
b7b447fd |
|
30-Dec-2021 |
Garance A Drosehn <gad@FreeBSD.org> |
When parsing a rule to rotate log files on a specific week day, parseDWM() can advance the time to the next week. If the next week is in the next month, then tm_mon is incremented. However, the increment was failing to handle the wraparound from December to January, so when parsing a rule during the last week of the December, the month would advance to month 12. This triggered an out-of-bounds read of the mtab[] array in days_pmonth() after parseDWM() returned. To fix, this change resets the month to January and increment the year when the month increment wraps. The default rule for /var/log/weekly.log triggers this during the last week of December each year. Reported by: CHERI Obtained from: CheriBSD Reviewed by: jhb Sponsored by: The University of Cambridge, Google Inc. Differential Revision: <https://reviews.freebsd.org/D33687>
|
#
4c8f6471 |
|
24-Mar-2020 |
Mark Johnston <markj@FreeBSD.org> |
newsyslog: Add fallthrough comments to appease Coverity. CID: 1008165, 1008166, 1008167 MFC after: 1 week Sponsored by: The FreeBSD Foundation
|
#
b326fec4 |
|
26-May-2017 |
David Bright <dab@FreeBSD.org> |
Add newsyslog capability to write 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. Reviewed by: vangyzen, ngie Approved by: vangyzen (mentor) MFC after: 2 months Relnotes: yes Sponsored by: Dell EMC Differential Revision: https://reviews.freebsd.org/D10253
|
#
a7d5f7eb |
|
19-Oct-2010 |
Jamie Gritton <jamie@FreeBSD.org> |
A new jail(8) with a configuration file, to replace the work currently done by /etc/rc.d/jail.
|
#
fe0506d7 |
|
09-Mar-2010 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Create the altix project branch. The altix project will add support for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting is a two-module system, consisting of a base compute module and a CPU expansion module. SGI's NUMAFlex architecture can be an excellent platform to test CPU affinity and NUMA-aware features in FreeBSD.
|
#
d7f03759 |
|
19-Oct-2008 |
Ulf Lilleengen <lulf@FreeBSD.org> |
- Import the HEAD csup code which is the basis for the cvsmode work.
|
#
398faf12 |
|
07-Jun-2004 |
Garance A Drosehn <gad@FreeBSD.org> |
Drop the include for <stdint.h>, it was only needed when this was using __DECONST() for something, and that reference has been removed. Noticed by: Helge Oldach MFC after: 13 days
|
#
c3033287 |
|
03-Oct-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
Handle a 'const' parameter without using __DECONST(). MFC after: 14 days
|
#
6a1485e2 |
|
22-Sep-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
Restructure the time processing routines, mainly to fix up the "will trim at" message printed when the user requests '-v'. The previous code would often print the wrong time, such as: On Sept 22, run: newsyslog -nv /var/log/wtmp And see: will trim at Mon Sep 1 05:00:00 2003 correct msg: will trim at Wed Oct 1 05:00:00 2003 MFC after: 20 days
|
#
526d55a4 |
|
13-Sep-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
Correct the calculation of "a leap year" in parseDWM. The calculation would only match a leap year every 400 years. The parseDWM code first showed up in April 2000, so the first time this bug would cause any confusion is in Feb 2004. MFC after: 18 days
|
#
2f8d7c56 |
|
11-Sep-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
Move the parse8601 and parseDWM routines into a new ptime.c file. The only code-change is to add a "next_time" parameter to both routines (and that is not used yet). A later update will make "next_time" more useful. MFC after: 20 days
|