Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Bash script - find command with delete and exec
Top Forums Programming Bash script - find command with delete and exec Post 302995494 by RudiC on Thursday 6th of April 2017 10:50:57 AM
Old 04-06-2017
I'm pretty sure some structuring of your text with e.g. punctuation would certainly enhance readability and understandability. And, posting WHAT "doesn't" could point helpers in the right direction. What be the difference when running it with mindepth 2 as compared to mindepth 1?
Would it help to put the {} in front of the file name to be touched?

Code:
find  -mindepth 2 -type d -exec echo touch WARNING_everything_in_here_will_get_removed_in_14_days_time.txt {} \;
touch WARNING_everything_in_here_will_get_removed_in_14_days_time.txt ./test/test1
touch WARNING_everything_in_here_will_get_removed_in_14_days_time.txt ./test/test1/test3
touch WARNING_everything_in_here_will_get_removed_in_14_days_time.txt ./test/test2

find  -mindepth 1 -type d -exec echo touch {}/WARNING_everything_in_here_will_get_removed_in_14_days_time.txt \;
touch ./test/WARNING_everything_in_here_will_get_removed_in_14_days_time.txt
touch ./test/test1/WARNING_everything_in_here_will_get_removed_in_14_days_time.txt
touch ./test/test1/test3/WARNING_everything_in_here_will_get_removed_in_14_days_time.txt
touch ./test/test2/WARNING_everything_in_here_will_get_removed_in_14_days_time.txt

You might want to make sure everybody knows when the 14 days will be over ...
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

find command exec error

Hi All, i am writing a shell script in korn shell which deletes all the files in a directory once in every 10DAYS. the directory has different format files. the script has something like this; cd /home/data/pavi echo "Please Enter the Number of Days to search for" read DAYS... (2 Replies)
Discussion started by: pavan_test
2 Replies

2. UNIX for Advanced & Expert Users

Find command with prune and exec

Hi, I'm using the following command to get a list of files on the system. find /releases -type f -exec ls -l > /home/sebarry/list.txt '{}' \; however, its searching a directory I don't want it to search so I know I have to use prune but I don't seem to be able to get prune and exec to work... (1 Reply)
Discussion started by: Sebarry
1 Replies

3. Shell Programming and Scripting

find command with -exec

Hi People, I have a directory full of compressed files (.Z extention) In many of these files there is a string pattern (3800078163033) I want to find all file names which contain this string in their text. Regards, Abhishek (2 Replies)
Discussion started by: max29583
2 Replies

4. UNIX for Dummies Questions & Answers

Bash script to delete file input on command line

1) I wrote a script and gave the desired permissions using "chmod 755 scriptname". Now if i edit the script file, why do i need to set the permission again? Didn't i set the permission attribute.. or if i edit the file, does the inode number of file changes? 2) I am running my unix on a server... (1 Reply)
Discussion started by: animesharma
1 Replies

5. Shell Programming and Scripting

find command with -exec

Hi all, Please could someone help with the following command requirement. I basically need to find files NEWER than a given file and order the result on time. My attempt so far is as follows: find . -newer <file_name> -exec ls -lrt {} ;\ But I dont seem to get the right result... (12 Replies)
Discussion started by: jonnyd
12 Replies

6. UNIX for Dummies Questions & Answers

What does the '\' in find -exec command

Hi, I have two scripts that remove files. One works fine and is coded find -name "syst*" -mtime +1 -exec rm {} \; The other is almost the same - only thing missing is the '\'. On that script though I keep getting: rm syst1202.file ? etc Does the \ make that difference or is it a... (3 Replies)
Discussion started by: Grueben
3 Replies

7. Shell Programming and Scripting

Find and move command with exec

Hi all, I am trying to find files newer than a given file and them mv them to a new location. So I far I have: find . ! -newer <file_name> -exec ls -l {} \; and find . ! -newer <file_name> -exec mv /TEMP_LOCATION {} \; find is not liking this. Anyone know how to modify the last... (2 Replies)
Discussion started by: jonnyd
2 Replies

8. Programming

Script to monitor progress of find/exec command

hi all, i want to monitor the progress of a find and exec command, this is the code i use - find . -type f -exec md5sum {} \; >> /md5sums/file.txt this command works and produces a text file with all the md5sums but while running it doesnt show the progress is there anyway i can do this... (4 Replies)
Discussion started by: robertkwild
4 Replies

9. Shell Programming and Scripting

Linux find command seems to not transmit all the result to the '-exec command'

Hello. From a script, a command for a test is use : find /home/user_install -maxdepth 1 -type f -newer /tmp/000_skel_file_deb ! -newer /tmp/000_skel_file_end -name '.bashrc' -o -name '.profile' -o -name '.gtkrc-2.0' -o -name '.i18n' -o -name '.inputrc' Tha command... (3 Replies)
Discussion started by: jcdole
3 Replies

LEARN ABOUT SUNOS

touch

touch(1)							   User Commands							  touch(1)

NAME

       touch, settime - change file access and modification times

SYNOPSIS

       touch [-acm] [-r ref_file | -t time]  file...

       touch [-acm] [date_time] file...

       settime [-f ref_file] [date_time] file...

DESCRIPTION

       The touch utility sets the access and modification times of each file. The file operand is created if it does not already exist.

       The  time used can be specified by -t time, by the corresponding time fields of the file referenced by -r ref_file, or by the date_time op-
       erand. If none of these are specified, touch uses the current time (the value returned by the time(2) function).

       If neither the -a nor -m options are specified, touch updates both the modification and access times.

       A user with write access to a file, but who is not the owner of the file or a super-user, can change the modification and access  times	of
       that file only to the current time. Attempts to set a specific time with touch will result in an error.

       The settime utility is equivalent to touch -c [date_time] file.

OPTIONS

       The following options are supported in the touch and settime utilities:

   touch
       The following options are supported for the touch utility:

       -a	       Changes the access time of file. Does not change the modification time unless -m is also specified.

       -c	       Does not create a specified file if it does not exist. Does not write any diagnostic messages concerning this condition.

       -m	       Changes the modification time of file. Does not change the access time unless -a is also specified.

       -r ref_file     Uses the corresponding times of the file named by ref_file instead of the current time.

       -t time	       Uses the specified time instead of the current time. time will be a decimal number of the form:

		       [[CC]YY]MMDDhhmm[.SS]

		       where each two digits represent the following:

		       MM	 The month of the year [01-12].

		       DD	The day of the month [01-31].

		       hh	The hour of the day [00-23].

		       mm	The minute of the hour [00-59].

		       CC	The first two digits of the year.

		       YY	The second two digits of the year.

		       SS	The second of the minute [00-61].

		       Both  CC  and YY are optional. If neither is given, the current year will be assumed. If YY is specified, but CC is not, CC
		       will be derived as follows:

		       +-----------------------------------------------------------+
		       |If YY is:		      CC becomes:		   |
		       |	   69-99			   19		   |
		       |	   00-38			   20		   |
		       |	   39-68			 ERROR		   |
		       +-----------------------------------------------------------+
		       The resulting time will be affected by the value of the TZ environment variable. If the resulting time value  precedes  the
		       Epoch, touch will exit immediately with an error status. The range of valid times is the Epoch to January 18, 2038.

		       The  range  for	SS  is	[00-61] rather than [00-59] because of leap seconds. If SS is 60 or 61, and the resulting time, as
		       affected by the TZ environment variable, does not refer to a leap second, the resulting time will be  one  or  two  seconds
		       after a time where SS is 59. If SS is not given, it is assumed to be 0.

   settime
       The following option is supported for the settime utility:

       -f ref_file     Uses the corresponding times of the file named by ref_file instead of the current time.

OPERANDS

       The following operands are supported for the touch and settime utilities:

       file	       A path name of a file whose times are to be modified.

       date_time       Uses the specified date_time instead of the current time. This operand is a decimal number of the form:

		       MMDDhhmm[YY]

		       where each two digits represent the following:

		       MM	 The month of the year [01-12].

		       DD	The day of the month [01-31].

		       hh	The hour of the day [00-23].

		       mm	The minute of the hour [00-59].

		       YY	The second two digits of the year.

				YY  is	optional. If it is omitted, the current year will be assumed. If YY is specified, the year will be derived
				as follows:

		       +-----------------------------------------------------------+
		       |YY			      Corresponding Year	   |
		       |	   69-99		       1969-1999	   |
		       |	   00-38		       2000-2038	   |
		       |	   39-68			 ERROR		   |
		       +-----------------------------------------------------------+
		       If no -r option is specified, no -t option is specified, at least two operands are specified, and the first operand  is	an
		       eight-  or ten-digit decimal integer, the first operand will be assumed to be a date_time operand. Otherwise, the first op-
		       erand will be assumed to be a file operand.

USAGE

       See largefile(5) for the description of the behavior of touch when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes).

ENVIRONMENT VARIABLES

       See environ(5) for descriptions of the following environment variables that affect the execution of  touch:  LANG,  LC_ALL,  LANG,  LC_ALL,
       LC_CTYPE, LC_MESSAGES, and NLSPATH.

       TZ	Determine the timezone to be used for interpreting the time option-argument or the date_time operand.

EXIT STATUS

       The following exit values are returned:

       0	The touch utility executed successfully and all requested changes were made.

       >0	An error occurred.  The touch utility returned the number of files for which the times could not be successfully modified.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+
       |CSI			     |enabled			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       time(2), attributes(5), environ(5), largefile(5), standards(5)

NOTES

       Users  familiar	with  the  BSD	environment  will find that for the touch utility, the -f option is accepted but ignored. The -f option is
       unnecessary because touch will succeed for all files owned by the user regardless of the permissions on the files.

SunOS 5.10							    22 Jun 2001 							  touch(1)
All times are GMT -4. The time now is 11:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy