diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-March/023912.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-March/023912.html | 117 |
1 files changed, 117 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-March/023912.html b/zarb-ml/mageia-dev/2013-March/023912.html new file mode 100644 index 000000000..c7ff7a574 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-March/023912.html @@ -0,0 +1,117 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Apache doesn't always like restarting.... + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Apache%20doesn%27t%20always%20like%20restarting....&In-Reply-To=%3C1384657.qcsi0UBVVr%40localhost%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="023907.html"> + <LINK REL="Next" HREF="023871.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Apache doesn't always like restarting....</H1> + <B>AL13N</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Apache%20doesn%27t%20always%20like%20restarting....&In-Reply-To=%3C1384657.qcsi0UBVVr%40localhost%3E" + TITLE="[Mageia-dev] Apache doesn't always like restarting....">alien at rmail.be + </A><BR> + <I>Thu Mar 28 07:34:41 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="023907.html">[Mageia-dev] Apache doesn't always like restarting.... +</A></li> + <LI>Next message: <A HREF="023871.html">[Mageia-dev] Freeze push: lightdm 1.4.1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#23912">[ date ]</a> + <a href="thread.html#23912">[ thread ]</a> + <a href="subject.html#23912">[ subject ]</a> + <a href="author.html#23912">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 27 maart 2013 23:12:13 schreef Colin Guthrie: +[...] +><i> Are you absolutely sure it's not just apache resetting the value when +</I>><i> you don't set CoreDumpDirectory in your httpd.conf? +</I> +for me it was with libvirtd and on x86_64 setting coreLIMIT=infinity, made it a +soft limit to 0; and hard to unlimited, setting it to a lower value worked for +me. perhaps it was libvirtd doing this itself... allthough that seems +farfetched... it seemed more likely that setting max number was somehow broken +in systemd or below... + +><i> > moreover, the systemd is compiled without coredump functionality, and that +</I>><i> > seems to have an effect on this and disallows one to configure +</I>><i> > systemd-coredump (which isn't build nor packaged) for usage with +</I>><i> > integrated coredumps with the systemd-coredump-ctl executable, (which is +</I>><i> > packaged). +</I>><i> +</I>><i> This was a deliberate decision at the time. There were not sufficient +</I>><i> tools to extract coredumps from the journal logs and really the coredump +</I>><i> support should be separate from the coredump capturing and logging to +</I>><i> the journal anyway, so it shouldn't affect anything you're doing right +</I>><i> now (e.g. it shouldn't affect how you setup apache) +</I> +ok, but you can package it and not set it to be used... + +><i> The fact that systemd-coredump-ctl is build is IMO a bug, and one that +</I>><i> could very well be fixed upstream already (probably is) but I didn't +</I>><i> want to keep the rm in the %install section of the spec lest it was +</I>><i> accidentally left in there when we turn the feature on (when it's +</I>><i> generally more useful - i.e. you can store cores in a directory outside +</I>><i> of the journal etc etc.). +</I> +perhaps it wouldn't get left as you would have an additional executable, so +you'd have to change the file sections anyway... + +[...] +><i> As for the core dump support, I would be happy enough re-enabling it +</I>><i> again. I'm just not convinced that storing the dumps in the journal is a +</I>><i> great idea. I mean if you get a constantly crashing service, your logs +</I>><i> will fill up quickly and be rotated away quickly. I think the cores +</I>><i> should be stored outside of the journal. I can't remember off hand if +</I>><i> the patch that implemented this was finally committed or not - I'll have +</I>><i> a look and check. +</I> +i'm not saying it should be set as default, but if you have systemd-coredump- +ctl i think you should also have systemd-coredump ... + +and why not provide the service if people want to use it, as long as you don't +set the /proc thing, it doesn't get used, so... +</PRE> + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="023907.html">[Mageia-dev] Apache doesn't always like restarting.... +</A></li> + <LI>Next message: <A HREF="023871.html">[Mageia-dev] Freeze push: lightdm 1.4.1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#23912">[ date ]</a> + <a href="thread.html#23912">[ thread ]</a> + <a href="subject.html#23912">[ subject ]</a> + <a href="author.html#23912">[ 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> |