Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Need help improving my script.
Top Forums Shell Programming and Scripting Need help improving my script. Post 302970884 by bakunin on Wednesday 13th of April 2016 05:29:43 AM
Old 04-13-2016
Quote:
Originally Posted by garlandxj11
What is the difference in "+" instead of "\;" ? What about that would help with the speed? Sorry for my ignorance. I really am trying to learn as I go on this. Smilie
First off: no problem! There no dumb questions, just dumb answers, so don't be shy.

The difference is that "\;" will call the command named in "-exec" each time a file is found. For instance, let us suppose in the curent directory are 5 files, "a", "b", "c", "d" and "e" (and nothing else):

Code:
find . -type f -exec rm {} \;

This wil delete all the files, but it will delete every file individually. In fact this will be executed:

Code:
rm a
rm b
rm c
rm d
rm e

But "rm" can take a list of files as well and this:

Code:
find . -type f -exec rm {} +

would be the same as

Code:
rm a b c d e

The difference seems to be small, but the most time, when calling a command like "rm", is the loading and starting of the program, not its execution. Therefore, if the command is executed only every fifth time the speed gain will be quite noticeably.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
rangarasan
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

improving my script (find & replace)

Hi all, I have a script that scan files, find old templet and replace it with new one. #!/bin/ksh file_name=$1 old_templet=$2 new_templet=$3 # Loop through every file like this for file in file_name do cat $file | sed "s/old_templet/new_templet/g" > $file.new #do a global searce and... (8 Replies)
Discussion started by: amir_yosha
8 Replies

2. Shell Programming and Scripting

improving my script

Hi; I want to access our customer database to retreive all clients that have as language index 2 or 3 and take their client number. My input is a file containing all client numbers. i access the data base using a function call "scpshow". The total number of clients i want to scan is 400 000... (6 Replies)
Discussion started by: bcheaib
6 Replies

3. UNIX for Dummies Questions & Answers

Improving Unix Skills

Kindly any advice to improve my unix skills as electronic books i can download or valuable sites as this one etc... (3 Replies)
Discussion started by: sak900354
3 Replies

4. Shell Programming and Scripting

Improving this validate function

Hi guys, I use this function which was provided to me by someone at this site. It works perfectly for validating a users input option against allowed options.. example: validateInput "1" "1 3 4 5" would return 0 (success) function validateInput { input=$1 allowedInput=$2 for... (4 Replies)
Discussion started by: pyscho
4 Replies

5. Shell Programming and Scripting

Improving code by using associative arrays

I have the following code, and I am changing it to #!/bin/bash hasArgumentCModInfile=0 hasArgumentSrcsInfile=0 hasArgumentRcvsInfile=0 OLDIFS="$IFS" IFS="|=" # IFS controls splitting. Split on "|" and "=", not whitespace. set -- $* # Set the positional... (3 Replies)
Discussion started by: kristinu
3 Replies

6. Shell Programming and Scripting

Basic help improving for in loop

I'm obviously very new to this. I'm trying to write a simple for loop that will read the directory names in /Users and then copy a file into the same subdir in each user directory. I have this, and it works but it isn't great. #!/bin/bash HOMEDIRS=/Users/* for dirs in $HOMEDIRS; do if ];... (5 Replies)
Discussion started by: Heath_T
5 Replies

7. Shell Programming and Scripting

Help with improving korn shell script

I am primarily a SQA/Tester and new to korn shell. How can I improve the following script? #/bin/ksh SourceLocation=~/Scripts/Test/Source TrackerLocation=~/Scripts/Test/Tracker TargetLocation=rdbusse@rdbmbp:/Users/rdbusse/Scripts/Test/Target for file in $(cd $SourceLocation; ls) do ... (7 Replies)
Discussion started by: bayouprophet
7 Replies

8. Shell Programming and Scripting

Improving code

Gents, I did the below code to get an output (report) ,.. the code works fine but I believe it can be more shorted using better method. Please if you can help, to generate same output improving the code , will be great. here my code. # get diff in time awk '{$9=$8-prev8;prev8=$8;print... (8 Replies)
Discussion started by: jiam912
8 Replies

LEARN ABOUT SUSE

tmpwatch

TMPWATCH(8)						   System Administrator's Manual					       TMPWATCH(8)

NAME

       tmpwatch - removes files which haven't been accessed for a period of time

SYNOPSIS

       tmpwatch [-u|-m|-c] [-MUadfqstvx] [--verbose] [--force] [--all]
		      [--nodirs] [--nosymlinks] [--test] [--fuser] [--quiet]
		      [--atime|--mtime|--ctime] [--dirmtime] [--exclude path]
		      [--exclude-user user] time dirs

DESCRIPTION

       tmpwatch  recursively  removes  files  which haven't been accessed for a given time.  Normally, it's used to clean up directories which are
       used for temporary holding space such as /tmp.

       When changing directories, tmpwatch is very sensitive to possible race conditions and will exit with an error if one is detected.  It  does
       not follow symbolic links in the directories it's cleaning (even if a symbolic link is given as its argument), will not switch filesystems,
       skips lost+found directories owned by the root user, and only removes empty directories, regular files, and symbolic links.

       By default, tmpwatch dates files by their atime (access time), not their mtime (modification time). If files aren't being removed  when	ls
       -l implies they should be, use ls -u to examine their atime to see if that explains the problem.

       If  the	--atime,  --ctime  or  --mtime options are used in combination, the decision about deleting a file will be based on the maximum of
       these times.  The --dirmtime option implies ignoring atime of directories, even if the --atime option is used.

       The time parameter defines the threshold for removing files.  If the file has not been accessed for time, the file is  removed.	 The  time
       argument  is  a	number with an optional single-character suffix specifying the units: h for hours, d for days.	If no suffix is specified,
       time is in hours.

       Following this, one or more directories may be given for tmpwatch to clean up.

OPTIONS

       -u, --atime
	      Make the decision about deleting a file based on the file's atime (access time). This is the default.

	      Note that the periodic updatedb file system scans keep the atime of directories recent.

       -m, --mtime
	      Make the decision about deleting a file based on the file's mtime (modification time) instead of the atime.

       -c, --ctime
	      Make the decision about deleting a file based on the file's ctime (inode change time) instead of the atime;  for	directories,  make
	      the decision based on the mtime.

       -M, --dirmtime
	      Make  the  decision  about  deleting a directory based on the directory's mtime (modification time) instead of the atime; completely
	      ignore atime for directories.

       -a, --all
	      Remove all file types, not just regular files, symbolic links and directories.

       -d, --nodirs
	      Do not attempt to remove directories, even if they are empty.

       -f, --force
	      Remove files even if root doesn't have write access (akin to rm -f).

       -l, --nosymlinks
	      Do not attempt to remove symbolic links.

       -q, --quiet
	      Report only fatal errors.

       -s, --fuser
	      Attempt to use the "fuser" command to see if a file is already open before removing it.  Not enabled by default.	 Does help in some
	      circumstances, but not all.  Dependent on fuser being installed in /sbin.  Not supported on HP-UX or Solaris.

       -t, --test
	      Don't remove files, but go through the motions of removing them. This implies -v.

       -U, --exclude-user=user
	      Don't remove files owned by user, which can be an user name or numeric user ID.

       -v, --verbose
	      Print a verbose display. Two levels of verboseness are available -- use this option twice to get the most verbose output.

       -x, --exclude=path
	      Skip  path;  if path is a directory, all files contained in it are skipped too.  If path does not exist, it must be an absolute path
	      that contains no symbolic links.

SEE ALSO

       cron(1), ls(1), rm(1), fuser(1)

WARNINGS

       GNU-style long options are not supported on HP-UX.

AUTHORS

       Erik Troan <ewt@redhat.com>
       Preston Brown <pbrown@redhat.com>
       Nalin Dahyabhai <nalin@redhat.com>
       Miloslav Trmac <mitr@redhat.com>

4th Berkeley Distribution					  Fri Dec 14 2007						       TMPWATCH(8)
All times are GMT -4. The time now is 05:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy