Can you do remove core file based on what created them :(
Hi,
Currently, we have a Perl script from a third-party vendor that is generating core dumps. It has been reported. We can't turn off the script as it does generate some diagnostic file that's required. So at the moment, we have to let it continue to do its run.
I wish I can say the vendor is dependable enough to help us cleanup the core dumps but unfortunately they aren't, hence am here asking for help.
Is it possible to check that the core dump belongs to this script or were generated by this script before removing it? I can do a non-recursive find below and change the ls -l to a rm
But I am a bit concern that I may remove core files that we needed that belong to other processes? Also, how do I change the regex so that is does a find fo core\.<numbers-only>
Hi There,
I was wondering how to manage files (ie. rm, cp , mv) based on date last modified and date created.
ie. Say i want to:
mv ./* ./temp/* (where the date created < 29/1/2006 )
or
mv ./* ./temp/* (where the date modified > 27/1/2006 && date modified < 29/1/2006)
Thanks in... (1 Reply)
Whenever i send a mail like: mail <mail id>, a core file is created under /var/spool/mqueue/ path. This is increasing the space of the file system. Why is that core file get created. Does it happens normally. I am getting an errpt error as:
LABEL: CORE_DUMP
IDENTIFIER: B6048838
... (0 Replies)
So, this issue is driving me nuts! I was hoping to get a lending hand here...
I have 2 files:
file1.txt contains:
this is example1
this is example2
this is example3
this is example4
this is example5
file2.txt contains:
example3
example5
Basically, I need a script or command to... (4 Replies)
Hi Friends,
I have to create a new log file everyday and append it with content based on some keywords found in another log file.
Here is what I have tried so far...
grep Error /parentfolder/someLogFile.log >> /parentfolder
/Archive/"testlogfile_error_`date '+%d%m%y'`.txt"
grep error... (6 Replies)
I am trying to rename files based on the created/born date of the file. I Have a total of 4000 files that i am trying to do this with and would like it to be log_yyyymmddhh.gz right now the files are maillog.???.gz.
Can anyone point me in the right direction of how to get this done via scipt?
... (4 Replies)
When I try to remove the file which was created by another user through super user, I am getting the "override protection 644 " meesage.
Could you please anyone help me how will I delete the file without prmpting the override protection.
I have also given the permission (rwx) to the group as... (3 Replies)
1. The problem statement, all variables and given/known data:
When looking for corefiles, include any file with core in its name. (Some UNIX/Linux systems add the PID of the process that created the core to reduce the chances of overwriting an already existing core file that might be needed. The... (6 Replies)
here below is a part of the file
cat fileName.txt
NAME=APP-VA-va_mediaservices-113009-VA_MS_MEDIA_SERVER_NOT_PRESENT-S
FIXED=false
DATE= 2013-02-19 03:46:04.4
PRIORITY=HIGH
RESOURCE NAME=ccm113
NAME=APP-DS-ds_ha-140020-databaseReplicationFailure-S
FIXED=false
DATE= 2013-02-19... (4 Replies)
I am trying to use the two files shown below to either remove or rename contents in one of those files. If in file1.txt $5 matches $5 of file2.txt and the value in $1 of file1.txt is not "No Match" then that value is substituted for all values in $5 and $1 of file2.txt. If however in $1 ... (5 Replies)
We have a user where a process is behaving abnormally and crashing. It would be great if a core file was generated, but I don't see one.
user101671:/apps/ -$lscore -d
compression: on
path specification: on
corefile location: /opt/core
naming specification: off
There is no core file being... (3 Replies)
Discussion started by: netmaster
3 Replies
LEARN ABOUT FREEBSD
savecore
SAVECORE(8) BSD System Manager's Manual SAVECORE(8)NAME
savecore -- save a core dump of the operating system
SYNOPSIS
savecore -c [-v] [device ...]
savecore -C [-v] [device ...]
savecore [-fkvz] [-m maxdumps] [directory [device ...]]
DESCRIPTION
The savecore utility copies a core dump into directory, or the current working directory if no directory argument is given, and enters a
reboot message and information about the core dump into the system log.
The options are as follows:
-C Check to see if a dump exists, and display a brief message to indicate the status. An exit status of 0 indicates that a dump is
there, 1 indicates that none exists. This option is compatible only with the [-v] option.
-c Clear the dump, so that future invocations of savecore will ignore it.
-f Force a dump to be taken even if either the dump was cleared or if the dump header information is inconsistent.
-k Do not clear the dump after saving it.
-m maxdumps Maximum number of dumps to store. Once the number of stored dumps is equal to maxdumps the counter will restart from 0.
-v Print out some additional debugging information. Specify twice for more information.
-z Compress the core dump and kernel (see gzip(1)).
The savecore utility looks for dumps on each device specified by the device argument(s), or on each device in /etc/fstab marked as ``dump''
or ``swap''. The savecore utility checks the core dump in various ways to make sure that it is complete. If it passes these checks, it
saves the core image in directory/vmcore.# and information about the core in directory/info.#. For kernel textdumps generated with the
textdump(4) facility, output will be stored in the tar(5) format and named directory/textdump.tar.#. The ``#'' is the number from the first
line of the file directory/bounds, and it is incremented and stored back into the file each time savecore successfully runs.
The savecore utility also checks the available disk space before attempting to make the copies. If there is insufficient disk space in the
file system containing directory, or if the file directory/minfree exists and the number of free kilobytes (for non-superusers) in the file
system after the copies were made would be less than the number in the first line of this file, the copies are not attempted.
If savecore successfully copies the kernel and the core dump, the core dump is cleared so that future invocations of savecore will ignore it.
The savecore utility is meant to be called near the end of the initialization file /etc/rc (see rc(8)).
SEE ALSO gzip(1), getbootfile(3), textdump(4), tar(5), dumpon(8), syslogd(8)HISTORY
The savecore utility appeared in 4.1BSD.
Support for kernel textdumps appeared in FreeBSD 7.1.
BUGS
The minfree code does not consider the effect of compression or sparse files.
BSD December 17, 2012 BSD