Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I found a file called kcore in my /proc directory. It's huge (267MB). What is it... safe to delete? I wouldn't worry about it if my hard drive wasn't nearly full!
The /proc directory doesn't actually exist. It shows you the current processes. The kcore file is the kernel core. Since the directory doesn't actually exist, therefore neither does the file. You probably won't be able to delete it (not sure), but since it is effectively a non-existant file, doing so would not increase your harddisk space.
I may be wrong on this, in which case I will also learn from any more replies.
/proc directory is your physical RAM, so it is not on HD, it is in the system memory, you won't be able to remove the kcore file under any sircumstances unless you blow your RAM and system up. I was caught once with it too, I thought it was some sort of core dump file and I tried to track what went wrong and I tried to delete the file, because it is read-only I tried to chmod it so I can delete it, and guess what I had no luck chmod it at all.
Hehe cool thanks. I figured it was a core dump too. I was just a little iffy as to whether to mess with it or not. Guess I wouldn't of had any luck if I'd tried anyways!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.