02-28-2006
The find command will, by default recurse into subdirectories. If you want, you can run 'ls -l' instead of 'rm -f' to check if it is indeed recursing.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Frineds,
I want to delete a set of files which are older than 7 days from teh current date.I am totally enw to shell scripting, can anyone help me with a sample code to list out the files which are older and then remove them from the directory.
Please help
THanks
Viswa (5 Replies)
Discussion started by: svishh123
5 Replies
2. Shell Programming and Scripting
find /filearchive/ -type f -mtime +7 -exec rm weblogs*.log {} \;
This worked only if this comand is executed int he unix comand prompt, but when i put this in the shell script it is not recognizing the file.It says weblogs: No such file or directory
Am i doing anything wrong here ? (4 Replies)
Discussion started by: svishh123
4 Replies
3. Shell Programming and Scripting
Hi all,
I try to write shell script to the below requirement.
I have Hard coded the oratab location and take the list of databases from oratab and find out archive log locations for each database,
and list more than 3 days old files for each location and purge those.
... (2 Replies)
Discussion started by: mak_boop
2 Replies
4. Shell Programming and Scripting
Hello All,
I want to delete the files based on the days. like, Files available under directory /abc want to delete if they are older than 15 days.
Files available under directory /pqr want to delete if they are 7 days old and some files under directory /xyz should get deleted if they are... (5 Replies)
Discussion started by: ssachins
5 Replies
5. Shell Programming and Scripting
Hi Expert's,
I need your assitance in tunning one script. I have a mount point where almost 4848008 files and 864739 directories are present. The script search for specific pattern files and specfic period then delete them to free up space. The script is designed to run daily and its taking around... (19 Replies)
Discussion started by: senthil.ak
19 Replies
6. Shell Programming and Scripting
Hi All,
I am looking forward to create a unix shell script to purge the files.
The requirement is:
1) Do df -k and check the current space occupied for the /a1 folder.
2) If the space consumed is greater than 90 %, delete all the DEF* files from a subfolder /a1/archive.
Example:
df... (4 Replies)
Discussion started by: shilpa_acc
4 Replies
7. Shell Programming and Scripting
Hi
I have a requirement wherein i need to purge some directories.
I have more than 2000 directories where i need to keep data for 10 days and delete the rest. What i am looking for is an efficient way to achieve this.
There are four mount points from where i need to delete the files.
... (3 Replies)
Discussion started by: Apoorvbarwa
3 Replies
8. UNIX for Dummies Questions & Answers
Hi guys i am having following files in a directory
a_07:15:13.txt
a_07:16:13.txt
a_07:17:13.txt
a_07:18:13.txt
a_07:19:13.txt
a_date file will be created on a day to day basics so that it may pileup on a long go.So i need to create a logic so that the files will be gunzipped to a backup... (1 Reply)
Discussion started by: mohanalakshmi
1 Replies
9. Shell Programming and Scripting
I am using blow script :--
#!/bin/bash
FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not
if
then
# echo "process found"
exit 0;
else
echo "process not found"
exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ... (1 Reply)
Discussion started by: ketanraut
1 Replies
10. Shell Programming and Scripting
Hello all,
I am facing a weird issue while executing a code below -
#!/bin/bash
cd /wload/baot/home/baotasa0/sandboxes_finance/ext_ukba_bde/pset
sh UKBA_publish.sh UKBA 28082015 3
if
then
echo "Param file conversion for all the areas are completed, please check in your home directory"... (2 Replies)
Discussion started by: ektubbe
2 Replies
LEARN ABOUT MOJAVE
expire.ctl
EXPIRE.CTL(5) File Formats Manual EXPIRE.CTL(5)
NAME
expire.ctl - control file for Usenet article expiration
DESCRIPTION
The file /etc/news/expire.ctl is the default control file for the expire(8) program, which reads it at start-up. Blank lines and lines
beginning with a number sign (``#'') are ignored. All other lines should be in one of two formats.
The first format specifies how long to keep a record of fully-expired articles. This is useful when a newsfeed intermittently offers older
news that is not kept around very long. (The case of very old news is handled by the ``-c'' flag of innd(8).) There should only be one
line in this format, which looks like this:
/remember/:days
Where days is a floating-point number that specifies the upper limit to remember a Message-ID, even if the article has already expired.
(It does not affect article expirations.)
Most of the lines in the file will consist of five colon-separated fields, as follows:
pattern:modflag:keep:default:purge
The pattern field is a list of wildmat(3)-style patterns, separated by commas. This field specifies the newsgroups to which the line is
applied. Note that the file is interpreted in order, so that the last line that matches will be used. This means that general patterns
(like a single asterisk to set the defaults) should appear before specific group specifications.
The modflag field can be used to further limit newsgroups to which the line applies, and should be chosen from the following set:
M Only moderated groups
U Only unmoderated groups
A All groups
The next three fields are used to determine how long an article should be kept. Each field should be either a number of days (fractions
like ``8.5'' are allowed) or the word ``never.'' The most common use is to specify the default value for how long an article should be
kept. The first and third fields -- keep and purge -- specify the boundaries within which an Expires header will be honored. They are
ignored if an article has no Expires header. The fields are specified in the file as ``lower-bound default upper-bound,'' and they are
explained in this order. Since most articles do not have explicit expiration dates, however, the second field tends to be the most impor-
tant one.
The keep field specifies how many days an article should be kept before it will be removed. No article in the newsgroup will be removed if
it has been filed for less then keep days, regardless of any expiration date. If this field is the word ``never'' then an article cannot
have been kept for enough days so it will never be expired.
The default field specifies how long to keep an article if no Expires header is present. If this field is the word ``never'' then articles
without explicit expiration dates will never be expired.
The purge field specifies the upper bound on how long an article can be kept. No article will be kept longer then the number of days spec-
ified by this field. All articles will be removed after then have been kept for purge days. If purge is the word ``never'' then the arti-
cle will never be deleted.
It is often useful to honor the expiration headers in articles, especially those in moderated groups. To do this, set keep to zero,
default to whatever value you wish, and purge to never. To ignore any Expires header, set all three fields to the same value.
There must be exactly one line with a pattern of ``*'' and a modflags of ``A'' -- this matches all groups and is used to set the expiration
default. It should be the first expiration line.
For example,
## How long to keep expired history
/remember/:5
## Most things stay for two weeks
*:A:14:14:14
## Believe expiration dates in moderated groups, up to six weeks
*:M:1:30:42
## Keep local stuff for a long time
foo.*:A:30:30:30
HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 1.15, dated 1996/10/29.
SEE ALSO
expire(8), wildmat(3).
EXPIRE.CTL(5)