summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-February/022657.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2013-February/022657.html')
-rw-r--r--zarb-ml/mageia-dev/2013-February/022657.html123
1 files changed, 123 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-February/022657.html b/zarb-ml/mageia-dev/2013-February/022657.html
new file mode 100644
index 000000000..c1dfb62af
--- /dev/null
+++ b/zarb-ml/mageia-dev/2013-February/022657.html
@@ -0,0 +1,123 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Logging%20%2B%20Provides/Requires%20%28Re%3A%20%5BRFC%5D%20rsyslog%20vs%0A%20journalctl%29&In-Reply-To=%3C5114FF4E.8080109%40mageia.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="022655.html">
+ <LINK REL="Next" HREF="022658.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)</H1>
+ <B>Thomas Backlund</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Logging%20%2B%20Provides/Requires%20%28Re%3A%20%5BRFC%5D%20rsyslog%20vs%0A%20journalctl%29&In-Reply-To=%3C5114FF4E.8080109%40mageia.org%3E"
+ TITLE="[Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)">tmb at mageia.org
+ </A><BR>
+ <I>Fri Feb 8 14:36:14 CET 2013</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="022655.html">[Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)
+</A></li>
+ <LI>Next message: <A HREF="022658.html">[Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#22657">[ date ]</a>
+ <a href="thread.html#22657">[ thread ]</a>
+ <a href="subject.html#22657">[ subject ]</a>
+ <a href="author.html#22657">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>08.02.2013 15:19, Olav Vitters skrev:
+&gt;<i> On Fri, Feb 08, 2013 at 02:07:52PM +0100, Anne Nicolas wrote:
+</I>&gt;&gt;<i> Le 08/02/2013 13:14, Olav Vitters a &#233;crit :
+</I>&gt;&gt;&gt;<i> On Fri, Feb 08, 2013 at 10:31:42AM +0000, Colin Guthrie wrote:
+</I>&gt;&gt;&gt;&gt;<i> Q) Will we make persistent disk-based journals optional?
+</I>&gt;&gt;&gt;&gt;<i> Yes: Makes it harder to ask a consistent question to extract debug.
+</I>&gt;&gt;&gt;&gt;<i> No: Some people will moan.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> It is either persistent logging or logging in memory right? I assume
+</I>&gt;&gt;&gt;<i> people won't understand that it'll log anyways, just in memory. So no
+</I>&gt;&gt;&gt;<i> point in giving an option that does not do what people might expect.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Just one point about this. It was said during meeting that having
+</I>&gt;&gt;<i> journalctl by default could break some other software like fail2ban.
+</I>&gt;&gt;<i> This should be checked.
+</I>&gt;<i>
+</I>&gt;<i> Some software relies on /var/log/messages and as such syslog. Journal
+</I>&gt;<i> does not break anything. But if you then remove syslog, then result is
+</I>&gt;<i> that such things will break.
+</I>&gt;<i>
+</I>&gt;<i> Same for gnome-system-log. IMO we should fix that software which relies
+</I>&gt;<i> on /var/log/messages (before 3 and if found afterwards, provide
+</I>&gt;<i> updates). For unmaintained software, deal with it as any other.
+</I>&gt;<i>
+</I>&gt;<i> /var/log/messages usually contains this weeks log messages. It is pretty
+</I>&gt;<i> trivial to replace that with the output of journalctl.
+</I>&gt;<i>
+</I>
+I think the best thing for Mga3 is to both install journald and
+upgrade rsyslog too by sticking it on install medias.
+
+Then we add in Mga 3 release notes that for upgrades rsyslog
+will be upgraded, but new installs will only have journald,
+so people wanting / needing it _must_ install it manually.
+
+And we also add the in the notes that we *might* obsolete
+(but not remove from repos, to still keep it as an option)
+it during upgrades in coming mga releases if journald gains
+all the features needed to really replace rsyslog.
+So we suggest people start trying to see if journald can
+provide all that they need.
+
+As a side note...
+when journald was first introduced I had the &quot;what for...&quot;
+reaction too as I was so used to grepping syslogs for
+stuff I needed... :)
+
+But now when I have gotten used to journalctl and the power
+of it, I dont really need the old logs anymore :)
+
+--
+Thomas
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="022655.html">[Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)
+</A></li>
+ <LI>Next message: <A HREF="022658.html">[Mageia-dev] Logging + Provides/Requires (Re: [RFC] rsyslog vs journalctl)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#22657">[ date ]</a>
+ <a href="thread.html#22657">[ thread ]</a>
+ <a href="subject.html#22657">[ subject ]</a>
+ <a href="author.html#22657">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>