I am not familiar with the V/88 system, so I can only guess at an answer....
What are the time stamps on these files? Try running:
This will show you the last modification times on these files followed by the last time they were accessed (assuming your version of 'ls' uses the standard options, check your man pages). If they havent been used in a while its probably safe to delete them. (Make sure you have a backup just in case!)
please help me, what can i do with the bountiful amount of core files our systems seem to have on occassional basis?? how do I analyze it and determine why the core file was dumped by the application that dumped it. the operating systems we use are solaris, DG-UX and linux red hat systems. (5 Replies)
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)
Does anyone know any tools or how to really get something out of a core file.
I can use strings and look for certain things like out of memory.
I am trying to use adb but I can't make heads or tails from it. I guess it is my lack of know how with the adb/mdb debugger.
anything would... (3 Replies)
Hi,
I am trying to delete a load of core files, but make sure I only delete core files. The system I am using has many files with core in the name, so I obviously can not simply search for "core".
I have tried using the 'find' command with pattern matching via , and know that his is the way... (3 Replies)
Hello *!
Just a short question. Where on the system i can find core files. I have one SUN server (Solaris 8) and from time to time I must clean core files on it. But i am not sure where i can find those files. Thank you in advance. :) (5 Replies)
Hi,
We have an application ASPA . The application related processes are running in /ASPA/bin directory . now whenever a process terminates abruptly , a core file should be generated (correct me if i am wrong) in the
/ASPA/bin directory . But i am not able to see any such files . The... (4 Replies)
Hi,
I am trying to use "find / -name core -print | xargs rm -f " ,but it would delete all core files including some core files we do not want to delete.
I search privious posts,someone said "To check what a core file came from - use the file command"
I used man page to search file command,but... (9 Replies)
In sun solaris whenever a jvm crashes we used to get the core file generated in binary format. We convert this core file to human readable format using
pstack corefile >> log
How can we convert the core file generated in HPUX to human readable format ? We dont have pstack either. (11 Replies)
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
LEARN ABOUT BSD
savecore
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 DistributionSAVECORE(8)