User Details
- User Since
- May 14 2014, 3:53 AM (611 w, 4 d)
Yesterday
Sat, Jan 31
Add regression test for installing empty files.
Fri, Jan 30
Thu, Jan 29
Wed, Jan 28
Sun, Jan 25
Wed, Jan 21
Tue, Jan 20
Address des@'s review: Use putenv() instead of duplicating the work.
Mon, Jan 19
Sun, Jan 18
Address des@'s comment: Move application of PAM environment to a better place.
Sat, Jan 17
Wed, Jan 14
Sat, Jan 10
Thu, Jan 8
Sun, Jan 4
Jan 1 2026
Dec 30 2025
Dec 29 2025
Dec 28 2025
Dec 27 2025
Dec 23 2025
Dec 22 2025
Dec 16 2025
Dec 9 2025
Dec 7 2025
Dec 4 2025
Nov 30 2025
Nov 13 2025
Nov 11 2025
Nov 10 2025
Nov 6 2025
Nov 5 2025
I think what bz@ really wanted is something like:
Nov 3 2025
Oct 31 2025
Oct 23 2025
Oct 15 2025
Oct 14 2025
Oct 13 2025
Oct 10 2025
Oct 2 2025
Sep 29 2025
Sep 28 2025
The current logic looks like it was effectively rounding the elapsed time to the nearest hour (with a 30-minute bias). That means a file only 30 minutes old could be considered "1 hour old," which isn’t what a user would normally expect if they configured rotation every hour. A user would reasonably expect “1h” to mean exactly 60 minutes, with perhaps a small tolerance for cron jitter or a slow rotation run.
I like the change in general, but if I was you I'd probably use getopt_long() and call the option --signal (consider this as an optional suggestion; I don't have strong opinion with this choice), because -I was somewhat counterintuitive to me as a flag to specify signal and both -s and -S were already occupied.
Sep 22 2025
Sep 21 2025
Sep 19 2025
Sep 16 2025
Sep 14 2025
Sep 3 2025
For those examining the history of newsyslog(8) and the removal of the -c command-line option, I feel it's important to understand the underlying design philosophy that motivated this and related changes. The goal was to establish a more robust, flexible, and administrator-friendly configuration model.