From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-December/010141.html | 102 +++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010141.html (limited to 'zarb-ml/mageia-dev/2011-December/010141.html') diff --git a/zarb-ml/mageia-dev/2011-December/010141.html b/zarb-ml/mageia-dev/2011-December/010141.html new file mode 100644 index 000000000..037c8674a --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010141.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] Enable kernel log timestamps? + + + + + + + + + +

[Mageia-dev] Enable kernel log timestamps?

+ Thomas Backlund + tmb at mageia.org +
+ Sat Dec 3 19:26:24 CET 2011 +

+
+ +
03.12.2011 18:22, Anssi Hannula skrev:
+> Hi!
+>
+> I propose to we configure our kernel to emit timestamps in kernel messages.
+>
+> + This allows quickly seeing the timing of kernel messages when using
+> the "dmesg" command.
+> + Allows to quickly see which msgs come from kernel when other
+>    processes (like systemd) inject messages there.
+> + Others are doing it AFAIK.
+> - Causes longer log lines
+>
+
+
+I'm not sure I like to enable it by default as it also makes it a pain 
+to compare 2 dmesgs as you cant do a simple diff anymore.
+
+Whats more, it can be enabled dynamically when really needed by adding 
+"printk.time=1" to the kernel command line.
+
+I used to have it enabled in kernel-tmb during
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1