{SOLVED} Delete core dumps?
{SOLVED} Delete core dumps?
Since installing GhostBSD 12.2 a few days ago I've got several core dump files in my home folder. Can I delete them? They average about 40Mb in size each.
Last edited by JTJersey on Wed Apr 14, 2021 7:53 pm, edited 1 time in total.
Re: Delete core dumps?
From time to time I delete the core dump files in my home folder.
Have not seen any problems with it so far...
Have not seen any problems with it so far...
Re: Delete core dumps?
It is save to delete.
Re: Delete core dumps?
You can remove dumpon and savecore from boot services.
Code: Select all
rc-update delete savecore boot
rc-update delete dumpon boot
Re: Delete core dumps?
Very nice. Thank you, this is what I have been looking for quite a while.
Re: Delete core dumps?
Not being a programmer, how do I implement those two lines of code? In a terminal gets me this: rc-update: service `savecore' is not in the runlevel `boot'
Re: Delete core dumps?
You use them simply in a terminal, that's right. You need superuser rights:
'sudo rc-update delete dumpon boot'
In a terminal 'rc-update' without option shows all runlevels and services.
If `savecore' is not listed in the output, it will not getting started at boot.
There is a detailled explanation in the wiki:
rc-update
'sudo rc-update delete dumpon boot'
In a terminal 'rc-update' without option shows all runlevels and services.
If `savecore' is not listed in the output, it will not getting started at boot.
There is a detailled explanation in the wiki:
rc-update
Re: Delete core dumps?
Did try that as superuser, but got same message about not being in runlevel boot. rc-update in a terminal doesn't list either savcore or dumpon services, so I guess something else is causing the core dump files to show up in my Home folder.
Re: Delete core dumps?
Just run rc-update by itself it will give you the list of services and at what level they are.
also, savecore might not be set up.
also, savecore might not be set up.
Re: Delete core dumps?
Thanks. I appreciate your taking time to respond. This is all I've got after running rc-update.
System Log Viewer/messages shows me this, if it's of any use to you. I've gotten this same message for every day I've booted the system.
Apr 10 13:15:43 gnome-keyring-daemon[3541]: couldn't access control socket: /var/run/user/1002/keyring/control: No such file or directory
Apr 10 13:15:43 mate-session[3520]: WARNING: Unable to find provider '' of required component 'dock'
Apr 10 13:15:44 gnome-keyring-daemon[3541]: The Secret Service was already initialized
Apr 10 13:15:44 gnome-keyring-daemon[3541]: The PKCS#11 component was already initialized
Apr 10 13:15:44 gnome-keyring-daemon[3541]: The SSH agent was already initialized
![Image]()
System Log Viewer/messages shows me this, if it's of any use to you. I've gotten this same message for every day I've booted the system.
Apr 10 13:15:43 gnome-keyring-daemon[3541]: couldn't access control socket: /var/run/user/1002/keyring/control: No such file or directory
Apr 10 13:15:43 mate-session[3520]: WARNING: Unable to find provider '' of required component 'dock'
Apr 10 13:15:44 gnome-keyring-daemon[3541]: The Secret Service was already initialized
Apr 10 13:15:44 gnome-keyring-daemon[3541]: The PKCS#11 component was already initialized
Apr 10 13:15:44 gnome-keyring-daemon[3541]: The SSH agent was already initialized