diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-February/022527.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-February/022527.html | 141 |
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-February/022527.html b/zarb-ml/mageia-dev/2013-February/022527.html new file mode 100644 index 000000000..0f55d27ab --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/022527.html @@ -0,0 +1,141 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [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%20%5BRFC%5D%20rsyslog%20vs%20journalctl&In-Reply-To=%3C51123DA7.4040804%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="022714.html"> + <LINK REL="Next" HREF="022529.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] rsyslog vs journalctl</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20rsyslog%20vs%20journalctl&In-Reply-To=%3C51123DA7.4040804%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] [RFC] rsyslog vs journalctl">mageia at colin.guthr.ie + </A><BR> + <I>Wed Feb 6 12:25:27 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="022714.html">[Mageia-dev] [RFC] rsyslog vs journalctl +</A></li> + <LI>Next message: <A HREF="022529.html">[Mageia-dev] [RFC] rsyslog vs journalctl +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22527">[ date ]</a> + <a href="thread.html#22527">[ thread ]</a> + <a href="subject.html#22527">[ subject ]</a> + <a href="author.html#22527">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Anne Nicolas at 06/02/13 08:43 did gyre and gimble: +><i> There was a discussion yesterday evening in packager meeting about what +</I>><i> we should do with rsyslog. It's needed for upgrade from Mageia 2. But +</I>><i> journalctl is now installed by default. +</I>><i> +</I>><i> Is there some requirement for systemd ? Shall we have both installed? We +</I>><i> need an answer to deal with upgrade and isos +</I> +At present the main systemd package provides "syslog" and also creates +the folder /var/log/journal which is what enables persistent logging +with the journal (without this folder it just logs into /run/log/journal +and keeps it in memory rotating away as needed over time) + +I did this to push the journal generally in cauldron and get it used and +see how things go. + +If required, I can split this into a separate package +(systemd-persistent-journal-logging) which simply provides "syslog" and +the folder /var/log/journal + +This would allow users to pick whether they want persistent logging with +journal or rsyslog (vs. the current choice of only being able to pick +rsyslog *in addition* to persistent logging). + + +An alternative is to simply document to people how to change the journal +space requirements such that even if persistent logging is enabled, it +will not take up too much room and purge itself quite aggressively. + + +I suppose the final decision should be based on what kind of experience +we ultimately want to provide in our tools. If I get a chance I can take +a quick look at the drakservices and draklog to see what simple stuff I +could hack in. The options for really nice, service-specific log +searching and viewing are really opened if we force the journal +persistent logs. + + +So if I were to choose, I'd leave everything as it is. Persistent +journal logging is enabled always but rsyslog is available as an option. + +This also has the advantage of meaning we, as bug triagers and +debuggers, always know where to look for extracting the relevant logs. +As Thomas mentioned to me over the weekend, we need a consistent command +to extract the needed info. I said that I would work on ensuring such a +command was included and thus available on the live media too should +people need to use that to boot a broken machine to extract debug info. + + +But I am also happy to concede to popular opinion here. + +Col + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="022714.html">[Mageia-dev] [RFC] rsyslog vs journalctl +</A></li> + <LI>Next message: <A HREF="022529.html">[Mageia-dev] [RFC] rsyslog vs journalctl +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22527">[ date ]</a> + <a href="thread.html#22527">[ thread ]</a> + <a href="subject.html#22527">[ subject ]</a> + <a href="author.html#22527">[ 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> |