Sponsored Content
Full Discussion: Cleaning core files
Top Forums UNIX for Dummies Questions & Answers Cleaning core files Post 302102524 by Tornado on Thursday 11th of January 2007 03:56:11 AM
Old 01-11-2007
To avoid errors from core directories use this:
Code:
# find / -name core -type f -exec rm {} \;

Tornado
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

core files

ok heres a question, :confused: well obviously i have here my old old motorola system V/88 in my /usr/adm folder i have a file called kernelcore which is 16mb (the computer has 16mb ram too), we believe this is the contents of our ram when the system crashed back in feb last year! Is it save... (2 Replies)
Discussion started by: Vodor
2 Replies

2. UNIX for Dummies Questions & Answers

Cleaning text files

I wish to clean a text file of the following characters 1/2, 1/4, o (degrees) I cant display these characters. I have tried ALT+189 etc (my terminal emulator is set to ASCII). How do I display the above ? I am using HP UX 10. (5 Replies)
Discussion started by: ferretman
5 Replies

3. UNIX for Advanced & Expert Users

What can be done with core files???

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)
Discussion started by: TRUEST
5 Replies

4. UNIX for Dummies Questions & Answers

cleaning log files

Say I have a log file called is there a way to clean out certain files in this log by or when I go to VI this file it tells me and I am guessing this means the file has become to large to append with VI so I was wondering if there was command with some argument to clean this out? Thanks ... (6 Replies)
Discussion started by: rocker40
6 Replies

5. 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

6. Shell Programming and Scripting

Cleaning the content of log files

Hi, I am facing problems while trying to clean a log file(Means making its file Size zero). I am not the owner of this file. From the command line, I can clean it by becoming a Sudo. (">logfilename"). I want to automate it using perl. But inside a script, sudo somehow doesnt seem to work. ... (1 Reply)
Discussion started by: jyotipg
1 Replies

7. UNIX for Dummies Questions & Answers

hp ux core files

what are core files?? Can I safely delete them??? Please, help (2 Replies)
Discussion started by: ldaliosmane
2 Replies

8. UNIX for Dummies Questions & Answers

How to know where the core files come from?

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)
Discussion started by: lemon_06
9 Replies

9. Shell Programming and Scripting

cleaning up files using find...

I am trying to cleanup a directory with around 4000 files, and using the below command to delete all .gz files older than 60 days, I am having the same issue of arguments being too long. is there a way i can use the same command to do what I intend to do. find /opt/et/logs/Archive/*.log.*.gz... (4 Replies)
Discussion started by: Shellslave
4 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
lib::core::only(3pm)					User Contributed Perl Documentation				      lib::core::only(3pm)

NAME
lib::core::only - Remove all non-core paths from @INC to avoid site/vendor dirs SYNOPSIS
use lib::core::only; # now @INC contains only the two core directories To get only the core directories plus the ones for the local::lib in scope: $ perl -Mlib::core::only -Mlocal::lib=~/perl5 myscript.pl To attempt to do a self-contained build (but note this will not reliably propagate into subprocesses, see the CAVEATS below): $ PERL5OPT='-Mlib::core::only -Mlocal::lib=~/perl5' cpan DESCRIPTION
lib::core::only is simply a shortcut to say "please reduce my @INC to only the core lib and archlib (architecture-specific lib) directories of this perl". You might want to do this to ensure a local::lib contains only the code you need, or to test an App::FatPacker tree, or to avoid known bad vendor packages. You might want to use this to try and install a self-contained tree of perl modules. Be warned that that probably won't work (see "CAVEATS"). This module was extracted from local::lib's --self-contained feature, and contains the only part that ever worked. I apologise to anybody who thought anything else did. CAVEATS
This does not propagate properly across perl invocations like local::lib's stuff does. It can't. It's only a module import, so it only affects the specific perl VM instance in which you load and import() it. If you want to cascade it across invocations, you can set the PERL5OPT environment variable to '-Mlib::core::only' and it'll sort of work. But be aware that taint mode ignores this, so some modules' build and test code probably will as well. You also need to be aware that perl's command line options are not processed in order - -I options take effect before -M options, so perl -Mlib::core::only -Ilib is unlike to do what you want - it's exactly equivalent to: perl -Mlib::core::only If you want to combine a core-only @INC with additional paths, you need to add the additional paths using -M options and the lib module: perl -Mlib::core::only -Mlib=lib # or if you're trying to test compiled code: perl -Mlib::core::only -Mblib For more information on the impossibility of sanely propagating this across module builds without help from the build program, see http://www.shadowcat.co.uk/blog/matt-s-trout/tainted-love <http://www.shadowcat.co.uk/blog/matt-s-trout/tainted-love> - and for ways to achieve the old --self-contained feature's results, look at App::FatPacker's tree function, and at App::cpanminus's --local-lib-contained feature. AUTHOR
Matt S. Trout <mst@shadowcat.co.uk> LICENSE
This library is free software under the same terms as perl itself. COPYRIGHT
(c) 2010 the lib::core::only "AUTHOR" as specified above. perl v5.14.2 2011-02-18 lib::core::only(3pm)
All times are GMT -4. The time now is 09:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy