summaryrefslogtreecommitdiff
path: root/src/shared/logs-show.h
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2023-02-07 11:20:24 +0100
committerLennart Poettering <lennart@poettering.net>2023-02-07 15:52:22 +0100
commit4e30b87d941c567509d0239dc30f993d0ac9dc1b (patch)
tree601af5ca2074e1cd9c3f0d1ff7ab6ee2463c746c /src/shared/logs-show.h
parent8586e8ab84b46d22ce904a84b6f1c3f798dad24e (diff)
downloadsystemd-4e30b87d941c567509d0239dc30f993d0ac9dc1b.tar.gz
logs-show: rename "ts" paramater/variable to "display_ts"
When displaying log data we deal with two kind of timestamps: the one we use for display (typically the source timestamp if available), and the one we use internally (typically the reception timestamp of journald). The user-facing output modes generally use the display timestamp, the ones intended for further processing (i.e. json + export outputs) do not, and directly query the timestamps of the entry, ignoring the source. This gets a bit confusing, since it's not always clear why we use which timestamp where. Let's address that by renaming the generic "ts" parameter/variable to "display_ts" to emphasize that the stored timestamp are "corrected" timestamps for display only. No real code change, just some renaming.
Diffstat (limited to 'src/shared/logs-show.h')
-rw-r--r--src/shared/logs-show.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/shared/logs-show.h b/src/shared/logs-show.h
index a15bda6886..df06b1c0f7 100644
--- a/src/shared/logs-show.h
+++ b/src/shared/logs-show.h
@@ -21,7 +21,7 @@ int show_journal_entry(
Set *output_fields,
const size_t highlight[2],
bool *ellipsized,
- dual_timestamp *previous_ts,
+ dual_timestamp *previous_display_ts,
sd_id128_t *previous_boot_id);
int show_journal(
FILE *f,