Sponsored Content
Top Forums Shell Programming and Scripting Listing files older than 2 months Post 13337 by LivinFree on Wednesday 16th of January 2002 12:49:08 AM
Old 01-16-2002
You should put some sort of qualifier in the -name option, like -name "*.logfile", depending on the naming scheme you're going for. If there isn't one, you can leave the -name "*" off altogether, as it will ignore any files beginning with "."... Unless that's what you're going for. It's also a good idea to simply move all the files to their own directory first, then examine them to make sure you aren't getting rid of anything important before removing them.

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Find files older than 5 days and remove tem after listing

need help with this ... Find files older than 5 days and remove tem after listing list "test" file older than 5 days and then remove them (1 Reply)
Discussion started by: ypatel6871
1 Replies

2. Shell Programming and Scripting

Delete files older than 3 months.(read date from the name of the file)

Guys, My log files stored in the date format format below(log_20080714072942): TIMESTAMP=`date +%Y%m%d%H%M%S` LOG=/log/log_${TIMESTAMP}.log I'm looking for a shell script which deletes all files which is older than 3 months from today. Regards, Bhagat (3 Replies)
Discussion started by: bhagat.singh-j
3 Replies

3. Shell Programming and Scripting

Listing processes that are a day older

Hi All, I am trying to automate some stuff to make my 'to-do-things' easier. I am in need for help regarding this. I have an output root 17187 3465 0 23:00:00 ? 0:01 Process1 root 4975 4974 0 May 12 ? 0:00 Process2 root 4042 16713 0 Jan 30 pts/22 0:00... (4 Replies)
Discussion started by: reddybs
4 Replies

4. Shell Programming and Scripting

gzip files older than 1 months

Hello, I want to gzip files in a folder in bulk i.e. all files older than 1 month should be in *.gz format. Could you please suggest how this can be achieved. Thanks. Regards, Alok (1 Reply)
Discussion started by: alok1301
1 Replies

5. Shell Programming and Scripting

need a code for moving the log files older than 2 months

Hi Viewer, I need logic code for moving the logs files from one directory to another directory. source :/xxxxxx/ xxxxxx / xxxxxx / xxxxxx / log --- under log directory we have so many files from last two years Here I need to check the files older than two months and I need to move in... (5 Replies)
Discussion started by: munna_su
5 Replies

6. Shell Programming and Scripting

Command to Count the files which is Older than 3 months?

Hi Gurus the count of files in a particular Directory... ls -lrth | grep -c ^- can any one share the command to Count the files which is Older than 3 months So please help me out in this Thanks in Advance (2 Replies)
Discussion started by: SeenuGuddu
2 Replies

7. HP-UX

listing processes older than n days

Hello; trying to find processes older than n days, mostly user shells Tried the following code on 11.31 box: in this case older than 5 days UNIX95= ps -ef -o user,pid,ppid,cpu,etime,stime | grep "-" | awk '{print $2}' | xargs ps -ef|grep -v '?' |\ awk '$5 !~ ""' | awk '($5 ~ "$(date "+%b")")... (6 Replies)
Discussion started by: delphys
6 Replies

8. UNIX and Linux Applications

Firefox 10 keeps losing history older than 2 months

Can anyone explain why Firefox 10 keeps losing history older than 2 months? (1 Reply)
Discussion started by: cokedude
1 Replies

9. Shell Programming and Scripting

Deleting files and directory's older than 3 months

I have a qnap TS259 that is running ubuntu. Have successfully setup back scripts that are initiated by cron. I would like to create a couple scrypts that would operate on the recycle bins for both drives. Just want to be able to run the script manually that would walk through both directories... (13 Replies)
Discussion started by: mackconsult
13 Replies

10. Shell Programming and Scripting

Listing files older than 30 days

Hi, Could someone help me that what the problem is in this code? #!/bin/sh FOLDER=/abc/datasource/checkstatus TIMESTAMP=$(date +%s) for filename in $(find $FOLDER -maxdepth 1 -type f -name "CHECK_STATUS*"); do f1=$($filename -Eo "{4}+") f2=$(date -d "$f1" +%s) if... (11 Replies)
Discussion started by: Home
11 Replies
FASTRM(8)						      System Manager's Manual							 FASTRM(8)

fastrm - quickly remove a set of files SYNOPSIS
fastrm [ -d ] [ -e ] [ -uN ] [ -sM ] [ -cI ] base_directory DESCRIPTION
Fastrm reads a list of files, one per line, from its standard input and removes them. If a file is not an absolute pathname, it is taken relative to the directory specified on the command line. The base_directory parameter must be a simple absolute pathname -- that is, it must not contain any ``/./'' or ``/../'' references. Fastrm is designed to be faster than the typical ``| xargs rm'' pipeline. For example, fastrm will usually chdir(2) into a directory before removing files from it. If the input is sorted, this means that most files to be removed will be simple names. Fastrm assumes that its input is valid and that it is safe to just do an unlink(2) call for each item to be removed. As a safety measure, if fastrm is run by root it will first stat(2) the item to make sure that it is not a directory before unlinking it. OPTIONS
-d If the ``-d'' flag is used then no files are removed. Instead a list of the files to be removed, in debug form, is printed on the standard output. Each line contains either the current directory of fastrm at the time it would do the unlink, and then the path name it would pass to unlink(2) as two fields separated by white space and a ``/'', or the absolute path name (a single field) of files it would unlink using the absolute path name. -e If the ``-e'' flag is used, fastrm will treat an empty input file (stdin) as an error. This is most useful when fastrm is last in a pipeline after a preceding sort(1) as if the sort fails, there will usually be no output to become input of fastrm. -u If the ``-u'' flag is used, then fastrm makes further assumptions about its work environment; in particular, that there are no sym- bolic links in the target tree. This flag also suggests that it is probably faster to reference the path ``../../../'' rather than start from the root and come down. (Note that this probably isn't true on systems that have a namei cache, which usually holds everything except ``..''). The optional N is an integer that specifies the maximum number of ``..'' segments to use -- paths that would use more than this use the absolute path name (from the root) instead. If the ``-u'' flag is given without a value, ``-u1'' is assumed. -s If the ``-s'' flag is used, then fastrm will perform the unlinks from one directory -- that is when a group of files in one direc- tory appear in the input consecutively -- in the order that the files appear in the directory from which they are to be removed. The intent of this flag is that on systems that have a per-process directory cache, finding files in the directory should be faster. It can have smaller benefits on other systems. The optional M is an integer that specifies the number of files that must be going to be removed from one directory before the files will be ordered. If the ``-s'' flag is given without a value, ``-s5'' is assumed. When the directory reordering is in use fastrm will avoid attempting to unlink files that it can't see in the directory, which can speed it appreciably when many of the file names have already been removed. -c The ``-c'' flag may be given to instruct fastrm when it should chdir(2). If the number of files to be unlinked from a directory is at least I then fastrm will chdir and unlink the files from in the directory. Otherwise it will build a path relative to its cur- rent directory. If ``-c'' is given without the optional integer I then ``-c1'' is assumed, which will cause fastrm to always use chdir. If ``-c'' is not used at all, then ``-c3'' is assumed. Use ``-c0'' to prevent fastrm from ever using chdir(2). -a -r There are also ``-a'' and ``-r'' options, which do nothing at all, except allow you to say ``fastrm -usa'' ``fastrm -ussr'' or ``fastrm -user''. These happen to often be convenient sets of options to use. EXIT STATUS
Fastrm exits with a status of zero if there were no problems, or one if something went wrong. Attempting to remove a file that does not exist is not considered a problem. If the program exits with a non-zero status, it is probably a good idea to feed the list of files into an ``xargs rm'' pipeline. HISTORY
This is revision 1.3, dated 1996/10/29. FASTRM(8)

Featured Tech Videos

All times are GMT -4. The time now is 11:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy