[opensuse-factory] Are the new systemd services notified somewhere?
Hi. I was updating packages on my netbook and I noticed a higher than usual CPU usage. When I checked the processes list I did find that systemd-coredump was using about 50% of the CPU. Are this kind of changes notified somewhere (apart from the list of changes after a snapshot where they're easy to overlook)? If not, could it be commented in the weekly review, please? Greetings. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Nov 3, 2015 at 3:45 PM, jcsl
Hi.
I was updating packages on my netbook and I noticed a higher than usual CPU usage. When I checked the processes list I did find that systemd-coredump was using about 50% of the CPU.
systemd-coredump ii a wrapper tool that can be used by the kernel to pipe a coredump into a program for further processing. In this case, to be accessed with coredumpctl. It may store coredumps in the journal or as a regular file (default) Are this kind of changes notified somewhere (apart
from the list of changes after a snapshot where they're easy to overlook)? If not, could it be commented in the weekly review, please?
If It went unnoticed in the status reports, you can always read the systemd package changelogs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Nov 03, 2015 at 04:09:33PM -0300, Cristian Rodríguez wrote:
On Tue, Nov 3, 2015 at 3:45 PM, jcsl
wrote: Hi.
I was updating packages on my netbook and I noticed a higher than usual CPU usage. When I checked the processes list I did find that systemd-coredump was using about 50% of the CPU.
systemd-coredump ii a wrapper tool that can be used by the kernel to pipe a coredump into a program for further processing. In this case, to be accessed with coredumpctl. It may store coredumps in the journal or as a regular file (default)
And if it shows 50% cpu time, another process is likely crashing in a loop like mad. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Cristian Rodríguez
-
jcsl
-
Marcus Meissner