Re: Need some small help on shell script - delete old files

steven_nospam at Yahoo! Canada wrote:
On Jun 14, 11:39 am, David <david4...@xxxxxxxxxxx> wrote:
On Jun 4, 5:02 pm, "steven_nospam at Yahoo! Canada"





<steven_nos...@xxxxxxxx> wrote:
On Jun 4, 11:01 am, David <david4...@xxxxxxxxxxx> wrote:
1.) I do not have subdirectories past the /home/tom64/public_html/cgi-
bin/arp3/backup directory. Please revise and confirm the best
command so that it does not search subdirectories past this directory
if that is important.
2.) Please look at my original script from the first message to this
post. For some reason, my script has not been gzipping these .sql
files. Any idea how to fix that so that they do get gzipped?
Thank you so very much!-
Here is what I would do if using your setup. Keep in mind, I tend to
use piped commands because my workload would rarely suffer from
performance issues, but some people may have a better way.
# START OF SAMPLE #
###################
BKPPATH=/home/tom64/public_html/cgi-bin/arp3/backup/
BKPFILE=$(/bin/date +"%Y-%b-%d").sql
#
# Do the current mysqldump
/usr/bin/mysqldump --opt -utom64 -pPaSSwoRD tom64 > ${BKPPATH}$
{BKPFILE}
#
# gzip any files that start with a number and end with sql
# this is sufficiently unique in the BKPPATH
cd ${BKPPATH}
ls | grep "^[0-9].*sql$" | xargs gzip

Better avoid the xargs in case of problematic file names:

cd $BKPPATH &&
find . -name "[0-9]*.sql" -type f -exec gzip {} \; -o \! -name . -prune

#
# Remove oldest backups from specified path - do NOT go into
subdirectories
# Anything older than 7 days with .sql.gz extension will be removed
# For testing purposes - you may replace "rm" command with "ls"
find ${BKPPATH} -name "*.sql.gz" -mtime +7 -print |
grep -v "${BKPPATH}.*/" |
xargs /bin/rm

Better avoid the xargs in case of problematic file names:

cd $BKPATH &&
find . -name "*.sql.gz" -type f -mtime +7 -exec rm -f {} \; \
-o \! -name . -prune

#################
# END OF SAMPLE #
The find command shows all files in the directory and subdirectories.
We then use grep -v to limit our view to files in the designated
directory by saying ignore any files that have the BKPPATH name along
with one or more characters (.*) and another slash (/). The results of
the grep are then sent to xargs to issue the rm command. The extra
gzip of $FILENAME at the end is not necessary as far as I can tell
because the ls will see that new file and gzip it in the ls | xargs
section.
CAVEAT: This was tested briefly on an IBM AIX 5.3 system in Korn Shell
and worked for me. It should naturally be tested on a test system
before being released to any production server. You may also want to
add additional checks, such as making sure your BKPPATH is set,
directory is not empty, etc. as I have not tried all possible
scenarios. Use at your own risk.
Regards,
SteveN
Dear SteveN,

I am running the script and have noticed that the file names have been
a bit strange. Getting (at times) double dumps at different times
during the same day. Could this possibly be from this script? I
have this script running on cron at 3:45am:
45 3 * * * pathtoscript

here is a list of the files in the backup directory:

-rw-r--r-- 1 growthtr growthtr 16668440 Jun 11 14:15 2009-
Jun-11-14-14-59.sql.gz
-rw-r--r-- 1 growthtr growthtr 16609994 Jun 11 03:45 2009-
Jun-11.sql.gz
-rw-r--r-- 1 growthtr growthtr 16694367 Jun 12 14:18 2009-
Jun-12-14-18-19.sql.gz
-rw-r--r-- 1 growthtr growthtr 16662433 Jun 12 03:45 2009-
Jun-12.sql.gz
-rw-r--r-- 1 growthtr growthtr 124439331 Jun 13 15:08 2009-
Jun-13-15-08-20.sql
-rw-r--r-- 1 growthtr growthtr 16716441 Jun 13 03:45 2009-
Jun-13.sql.gz
-rw-r--r-- 1 growthtr growthtr 124621863 Jun 14 03:45 2009-
Jun-14.sql

Any idea why I am getting two dumps like this annd that the dump files
with the longer file name are at irregular times?

Maybe another script creates the long file names?


Also, any idea why 2009-Jun-14.sql did not gzip from last night?


It was certainly created a second later than the script was run.
Created by whom? Yet another script?

--
echo imhcea\.lophc.tcs.hmo |
sed 's2\(....\)\(.\{5\}\)2\2\122;s1\(.\)\(.\)1\2\11g;1s;\.;::;2'
.

Relevant Pages