Cleaning up coredumpctl list
Clash Royale CLAN TAG#URR8PPP
up vote
13
down vote
favorite
I'm looking for a way to remove any trace of old coredumps in coredumpctl list
. At the moment it lists coredumps beginning at 2014-12-14 - I've updated software so often between then and now that I doubt those old coredumps are going to help me debug any problems now. Unfortunately removing the files from /var/lib/systemd/coredump
only made the asterisk in the "PRESENT" column of coredumpctls output disappear.
I couldn't find any way to remove all information about coredumps in the manpages or in the help output of coredumpctl.
systemd core-dump
add a comment |
up vote
13
down vote
favorite
I'm looking for a way to remove any trace of old coredumps in coredumpctl list
. At the moment it lists coredumps beginning at 2014-12-14 - I've updated software so often between then and now that I doubt those old coredumps are going to help me debug any problems now. Unfortunately removing the files from /var/lib/systemd/coredump
only made the asterisk in the "PRESENT" column of coredumpctls output disappear.
I couldn't find any way to remove all information about coredumps in the manpages or in the help output of coredumpctl.
systemd core-dump
add a comment |
up vote
13
down vote
favorite
up vote
13
down vote
favorite
I'm looking for a way to remove any trace of old coredumps in coredumpctl list
. At the moment it lists coredumps beginning at 2014-12-14 - I've updated software so often between then and now that I doubt those old coredumps are going to help me debug any problems now. Unfortunately removing the files from /var/lib/systemd/coredump
only made the asterisk in the "PRESENT" column of coredumpctls output disappear.
I couldn't find any way to remove all information about coredumps in the manpages or in the help output of coredumpctl.
systemd core-dump
I'm looking for a way to remove any trace of old coredumps in coredumpctl list
. At the moment it lists coredumps beginning at 2014-12-14 - I've updated software so often between then and now that I doubt those old coredumps are going to help me debug any problems now. Unfortunately removing the files from /var/lib/systemd/coredump
only made the asterisk in the "PRESENT" column of coredumpctls output disappear.
I couldn't find any way to remove all information about coredumps in the manpages or in the help output of coredumpctl.
systemd core-dump
systemd core-dump
asked Aug 5 '15 at 20:33
Wieland
3,8061527
3,8061527
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
7
down vote
It seems the metadata is kept in the systemd journal, so it is gone after
rm /var/log/journal/*/*
killall -9 systemd-journald
The downside is that all other syslog is gone as well.
Maybe the cleaner method would be the one given in How to clear journalctl
journalctl --vacuum-time=2d
add a comment |
up vote
0
down vote
First you may prune the journal discarding entries older than a day:
journalctl --vacuum-time=1d
Since "coredumpctl list" lists the dumpfiles recorded by the journal, you may manually delete the dump files from /var/lib/systemd/coredump that are not listed.
coredumpctl list
Browse the dump files, compare the files with the results from the command and delete the files not listed.
New contributor
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
It seems the metadata is kept in the systemd journal, so it is gone after
rm /var/log/journal/*/*
killall -9 systemd-journald
The downside is that all other syslog is gone as well.
Maybe the cleaner method would be the one given in How to clear journalctl
journalctl --vacuum-time=2d
add a comment |
up vote
7
down vote
It seems the metadata is kept in the systemd journal, so it is gone after
rm /var/log/journal/*/*
killall -9 systemd-journald
The downside is that all other syslog is gone as well.
Maybe the cleaner method would be the one given in How to clear journalctl
journalctl --vacuum-time=2d
add a comment |
up vote
7
down vote
up vote
7
down vote
It seems the metadata is kept in the systemd journal, so it is gone after
rm /var/log/journal/*/*
killall -9 systemd-journald
The downside is that all other syslog is gone as well.
Maybe the cleaner method would be the one given in How to clear journalctl
journalctl --vacuum-time=2d
It seems the metadata is kept in the systemd journal, so it is gone after
rm /var/log/journal/*/*
killall -9 systemd-journald
The downside is that all other syslog is gone as well.
Maybe the cleaner method would be the one given in How to clear journalctl
journalctl --vacuum-time=2d
edited Jan 19 '16 at 8:19
answered Jan 19 '16 at 8:11
Bernhard M.
9114
9114
add a comment |
add a comment |
up vote
0
down vote
First you may prune the journal discarding entries older than a day:
journalctl --vacuum-time=1d
Since "coredumpctl list" lists the dumpfiles recorded by the journal, you may manually delete the dump files from /var/lib/systemd/coredump that are not listed.
coredumpctl list
Browse the dump files, compare the files with the results from the command and delete the files not listed.
New contributor
add a comment |
up vote
0
down vote
First you may prune the journal discarding entries older than a day:
journalctl --vacuum-time=1d
Since "coredumpctl list" lists the dumpfiles recorded by the journal, you may manually delete the dump files from /var/lib/systemd/coredump that are not listed.
coredumpctl list
Browse the dump files, compare the files with the results from the command and delete the files not listed.
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
First you may prune the journal discarding entries older than a day:
journalctl --vacuum-time=1d
Since "coredumpctl list" lists the dumpfiles recorded by the journal, you may manually delete the dump files from /var/lib/systemd/coredump that are not listed.
coredumpctl list
Browse the dump files, compare the files with the results from the command and delete the files not listed.
New contributor
First you may prune the journal discarding entries older than a day:
journalctl --vacuum-time=1d
Since "coredumpctl list" lists the dumpfiles recorded by the journal, you may manually delete the dump files from /var/lib/systemd/coredump that are not listed.
coredumpctl list
Browse the dump files, compare the files with the results from the command and delete the files not listed.
New contributor
edited 23 hours ago
New contributor
answered 23 hours ago
megalith
11
11
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f220420%2fcleaning-up-coredumpctl-list%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password