From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [RFC pmg-log-tracker] do not assume constant year based on file index
Date: Mon, 3 Jan 2022 17:23:12 +0100 [thread overview]
Message-ID: <20220103162312.24335-1-s.ivanov@proxmox.com> (raw)
rather start with the current time at invocation and if the month in
the log is larger assume a year-wrap happened between logwriting and
invocation.
the old logic is flawed (but that can be said about parsing
traditional syslog timestamps (w/o year) in general) - it got worse
with the change in bullseye of rotating syslog weekly by default -
resulting in users losing one week of logs per day in the new year as
reported in https://forum.proxmox.com/threads/.102322/
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
Tested against a production system's log which did not yield any data
for the past weeks without the patch.
Sending as RFC since I'm sure to have overlooked a corner-case the previous
logic handled better?
Might break the use-case of a time-jump after a fresh reboot (if e.g. the
hardware-clock is far in the past/future) - else the assumption that the
logs are written in the past should hold
src/main.rs | 31 +++++++++++--------------------
1 file changed, 11 insertions(+), 20 deletions(-)
diff --git a/src/main.rs b/src/main.rs
index daf0738..c5a723a 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -1722,7 +1722,7 @@ struct Parser {
current_record_state: RecordState,
rel_line_nr: u64,
- current_year: [i64; 32],
+ current_year: i64,
current_month: i64,
current_file_index: usize,
@@ -1743,14 +1743,7 @@ struct Parser {
impl Parser {
fn new() -> Self {
- let mut years: [i64; 32] = [0; 32];
-
- for (i, year) in years.iter_mut().enumerate() {
- let mut ts = time::get_time();
- ts.sec -= (3600 * 24 * i) as i64;
- let ltime = time::at(ts);
- *year = (ltime.tm_year + 1900) as i64;
- }
+ let ltime = time::now();
Self {
sentries: HashMap::new(),
@@ -1760,8 +1753,8 @@ impl Parser {
smtp_tls_log_by_pid: HashMap::new(),
current_record_state: Default::default(),
rel_line_nr: 0,
- current_year: years,
- current_month: 0,
+ current_year: (ltime.tm_year + 1900) as i64,
+ current_month: ltime.tm_mon as i64,
current_file_index: 0,
count: 0,
buffered_stdout: BufWriter::with_capacity(4 * 1024 * 1024, std::io::stdout()),
@@ -1848,7 +1841,7 @@ impl Parser {
let (time, line) = match parse_time(
line,
- self.current_year[self.current_file_index],
+ self.current_year,
&mut self.current_month,
) {
Some(t) => t,
@@ -1938,7 +1931,7 @@ impl Parser {
}
if let Some((time, _)) = parse_time(
&buffer[0..size],
- self.current_year[i],
+ self.current_year,
&mut self.current_month,
) {
// found the earliest file in the time frame
@@ -1957,7 +1950,7 @@ impl Parser {
}
if let Some((time, _)) = parse_time(
&buffer[0..size],
- self.current_year[i],
+ self.current_year,
&mut self.current_month,
) {
if time < self.options.start {
@@ -2311,19 +2304,17 @@ fn parse_time<'a>(
let mut ltime: libc::time_t;
let mut year = cur_year;
- if *cur_month == 11 && mon == 0 {
- year += 1;
- }
- if mon > *cur_month {
- *cur_month = mon;
+ // assume smaller month now than in log line means yearwrap
+ if *cur_month < mon {
+ year -= 1;
}
ltime = (year - 1970) * 365 + CAL_MTOD[mon as usize];
+ // leap year considerations
if mon <= 1 {
year -= 1;
}
-
ltime += (year - 1968) / 4;
ltime -= (year - 1900) / 100;
ltime += (year - 1600) / 400;
--
2.30.2
next reply other threads:[~2022-01-03 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:23 Stoiko Ivanov [this message]
2022-01-04 13:15 ` [pmg-devel] applied: " Stoiko Ivanov
2022-01-03 17:39 [pmg-devel] " Dietmar Maurer
2022-01-03 18:05 ` Stoiko Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220103162312.24335-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox