Sponsored Content
Top Forums UNIX for Dummies Questions & Answers What are core files and how can I delete them when am performing system maintenance?? Post 18886 by LivinFree on Thursday 4th of April 2002 02:39:05 AM
Old 04-04-2002
I am self taught in Unix as well (as is painfully obvious in some of my assumptions past (and future)). However, I know for a fact in my experience that trying to learn every possible solution to every problem is not possible. You have to understand the system first, then create or figure out your own solutions. Yes, people get stumped sometimes. It's OK to ask for help. But no one will hold your hand for everything.

And if I do honestly think a question is obvious homework (and usually other believe the same) I do not hesitate to close the thread right away. This question may not be homework, but it's such a pointed and narrow question for such a broad subject that many people may take it to be homework.

Anyways, here's a website on old core memory, before the nifty little DIMMs / SIMMs used more recently:
http://www.psych.usyd.edu.au/pdp-11/core.html
Most systems now use moderm memory, but you'll still hear terms that are a throwback to this memory, like "core dump" or "in-core image".
A core file, or core dump, is basically an abnormally aborting process dumping all of it's physical memory to disk. It's useful for debugging. They are typically files called "core". If you use the command "file core", many systems will tell you what process created the file.

Getting rid of unnecessary core files is like taking out the trash at home - if it was never done, your kitchen would eventually fill up.
It may not slow your system down very much, like rotting fruit on your kitchen counter doesn't affect how long you have to bake your cookies, but then again, who wants rotting fruit on their counter?

There lots of maintenance you can be doing - cleaning up core files is one of them. There's also hardware maintenance, software upgrades, etc...

As for finding core files, run as root:
"find / -type f -name core > /tmp/core-list 2>/dev/null"
Next, examine each file to make sure it's not needed by a developer or system engineer, and delete the ones that are just taking up space.

And as for not liking the man pages, after a while, you'll probably start hearing a lot of people telling you to RTFM (Read The F***ing Manual). Man pages are a wonderful resource, and no Unix admin or guru can do without them. Learn how to effectively search the man pages (man -k keyword), and search google for answers, since many people have probably had similar questions in the past. Some systems also use the "info" program, which is like a newfangled man page system. It's a little more interactive, and almost navigatable like html, but frankly, I'll take a man page any day.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Quiet System for Maintenance

I have backups that run in a cron @ midnight. Does the backup utility make sure that the system is quiet --(no users are logged on) or do I need to add some stuff to make sure nobody is accessing those file while they are being backed up. (3 Replies)
Discussion started by: michieka
3 Replies

2. UNIX for Advanced & Expert Users

Analyzing System Core Files?

can some tell me how to do this. I mean, i tried finding this out on my own but when I checked the man pages, i got a truckload of commands available pertaining to this task which in turn got me confused. so my question is, if there is a simple straight forward(not necessarily easy) way to... (2 Replies)
Discussion started by: TRUEST
2 Replies

3. UNIX for Advanced & Expert Users

System Maintenance

How do I go about doing this??? Is there something to it other than cleaning up useless files?? if you have knowledge concerning this, please give your suggestions also, is it possible or safe to compress an entire filesystem. how do you go about doing this??? any information is appreciated (7 Replies)
Discussion started by: IMPORTANT
7 Replies

4. UNIX for Dummies Questions & Answers

system log files and core files?

Solaris v5.6 What log files should be checked out as part of your sys admin daily routine? I've printed out my syslog.conf file, and looked in /var/log and found authlog, syslog, and POPlog. I know of /var/adm/messages. What others should I be looking for? I know of the "find" command. I... (8 Replies)
Discussion started by: Westy564
8 Replies

5. Shell Programming and Scripting

how to delete files at booting of system (system startup)

hi all I have a problem how to write a shell script which delete files/folder form directory whenever system boot and copy last updated folder/file in the specified directory.pse help me ASAP. i write a script which copy files in directory.I want when system boot up using script it check whether... (1 Reply)
Discussion started by: shubhig15
1 Replies

6. UNIX for Dummies Questions & Answers

System maintenance weekly job and welcome message

Since a few weeks I am playing with debian and now I have 2 questions. The first one: I want to create weekly a file to all user directories. I know that you have a cronjob to schedule it weekly. In this cronjob I have written the following line: df >> /home/%users/diskspace.txt I've... (1 Reply)
Discussion started by: iceqube
1 Replies

7. UNIX for Advanced & Expert Users

slow performing system

Friends Greetings. I have a RedHat 5.7 64bit virtual server on VMware ESXi 4.1. This server and other Redhat Servers are running very slow. I did some stats collection on ESXi and looks like Linux is holding the disk IO. I am not sure what is causing this behavior. On Linux I checked the CPU... (4 Replies)
Discussion started by: sdewal
4 Replies

8. Solaris

System booting to maintenance mode

Hi Guys, I have a sunblade 1500. I booted the system and it booted to maintenance mode. How can I fix this? Thanks lots (8 Replies)
Discussion started by: cjashu
8 Replies

9. Solaris

Solaris 10 system boots into Maintenance mode

I have seen similar threads on this issue, but I have not seen a fix. Basically I am getting a lot of rcp bind errors. Below find the output of "svcs -xv". not sure where to begin: # svcs -xv svc:/network/rpc/bind:default (RPC bindings) State: maintenance since Fri May 25 14:13:18 2012... (14 Replies)
Discussion started by: brownwrap
14 Replies

10. UNIX for Beginners Questions & Answers

Should i delete core files ?

Good morning, i need your help please By searching some of the largest files i found some core files that take up much space This is the command: find ./ -type f -name core -exec file {} \; Output: ./xptol/tel/tasacion/CIERR/exe/core: ELF 64-bit MSB core file SPARCV9 Version 1, from... (2 Replies)
Discussion started by: alexcol
2 Replies
SAVECORE(8)						      System Manager's Manual						       SAVECORE(8)

NAME
savecore - save a core dump of the operating system SYNOPSIS
savecore dirname [ system ] DESCRIPTION
Savecore is meant to be called at the end of the /etc/rc file. Its function is to save the core dump of the system (if one was made) and to write a reboot message in the shutdown log. It saves the core image in the file dirname/core.n and its corresponding namelist in dirname/unix.n. The second argument is the namelist for the system which made the core image; the current system is always assumed to be /unix. The trailing ".n" in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before savecore writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the file sys- tem which contains dirname than the number obtained from the minfree file, the core dump is not done. If the minfree file does not exist, savecore always writes out the core file (assuming that a core dump was taken). Savecore also writes a reboot message in the shut down log. If the system crashed as a result of a panic, savecore records the panic string in the shut down log too. If savecore detects that the system time is wrong because of a crash (the time in the core image is after the current time), it will reset the system time to its best estimate of the time, which is the time in the core image plus the elapsed time since the reboot. It announces the time that it set when this occurs. FILES
/usr/adm/shutdownlogshutdown log /unix current UNIX BUGS
The method used to determine whether a dump is present, and to prevent the same core image from being saved multiple times, is not elegant. This information should be passed to init by the system; however, this is difficult because the system may have to be rebooted a second time if the root filesystem is patched. 3rd Berkeley Distribution SAVECORE(8)
All times are GMT -4. The time now is 05:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy