[Mageia-dev] Apache doesn't always like restarting....

Thu Mar 28 07:34:41 CET 2013

Op woensdag 27 maart 2013 23:12:13 schreef Colin Guthrie:
+[...]
+> Are you absolutely sure it's not just apache resetting the value when
+> you don't set CoreDumpDirectory in your httpd.conf?
+
+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...
+
+> > moreover, the systemd is compiled without coredump functionality, and that
+> > seems to have an effect on this and disallows one to configure
+> > systemd-coredump (which isn't build nor packaged) for usage with
+> > integrated coredumps with the systemd-coredump-ctl executable, (which is
+> > packaged).
+> 
+> This was a deliberate decision at the time. There were not sufficient
+> tools to extract coredumps from the journal logs and really the coredump
+> support should be separate from the coredump capturing and logging to
+> the journal anyway, so it shouldn't affect anything you're doing right
+> now (e.g. it shouldn't affect how you setup apache)
+
+ok, but you can package it and not set it to be used...
+
+> The fact that systemd-coredump-ctl is build is IMO a bug, and one that
+> could very well be fixed upstream already (probably is) but I didn't
+> want to keep the rm in the %install section of the spec lest it was
+> accidentally left in there when we turn the feature on (when it's
+> generally more useful - i.e. you can store cores in a directory outside
+> of the journal etc etc.).
+
+perhaps it wouldn't get left as you would have an additional executable, so 
+you'd have to change the file sections anyway...
+
+[...]
+> As for the core dump support, I would be happy enough re-enabling it
+> again. I'm just not convinced that storing the dumps in the journal is a
+> great idea. I mean if you get a constantly crashing service, your logs
+> will fill up quickly and be rotated away quickly. I think the cores
+> should be stored outside of the journal. I can't remember off hand if
+> the patch that implemented this was finally committed or not - I'll have
+> a look and check.
+
+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...
+