Sponsored Content
Top Forums UNIX for Dummies Questions & Answers find command on a empty directory - bad status Post 302970333 by deepakwins on Tuesday 5th of April 2016 01:53:13 PM
Old 04-05-2016
Thanks for the Clarification!

Quote:
Originally Posted by MadeInGermany
The + collects arguments (up to a certain limit) and runs one (or few) rm -f arg1 arg2 ...,
while the ; each time runs the program with one argument rm -f arg1; rm -f arg2; ....
This User Gave Thanks to deepakwins For This Post:
 

10 More Discussions You Might Find Interesting

1. Programming

How to find the exit status of last command in Unix?

Hi, I want to find the exit status of the last executed command in C Shell. Tried $? but getting the error Variable syntax...$? does not seem to work in C shell.. is there any other command in C shell to find the exit status of last command? Thanks in advance, raju (1 Reply)
Discussion started by: rajugp1
1 Replies

2. UNIX for Dummies Questions & Answers

how to find the exit status for the last executed command

I am executing a find command in my script i.e find $2 -type f -name '*.gif' -mtime +$1 -exec rm {} \; how do i check that this command is executed properly.. i would lke t trap the errror and display my error message kinly help.. this is an urgent issue. (1 Reply)
Discussion started by: vijay.amirthraj
1 Replies

3. UNIX for Dummies Questions & Answers

Getting same exit status for empty and non empty file

Hi All, I am checking for a empty input file to do some further action , but I am getting exit status 0 in both the cases , for empty and non empty file both. The value of $? is coming 0 in if part also and else part too. #!/bin/ksh if ]; then echo "data" # exit 0 echo "$?" else... (4 Replies)
Discussion started by: mavesum
4 Replies

4. UNIX for Advanced & Expert Users

Equivalents of tee command to find exit status of command

Hi, Want to log the output of command & check the exit status to find whether it succeeded or failed. > ls abc ls: abc: No such file or directory > echo $? 1 > ls abc 2>&1 | tee log ls: abc: No such file or directory > echo $? 0 Tee commands changes my exit status to be always... (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies

5. UNIX for Dummies Questions & Answers

Find command returning bad status--

would like to remove the post (8 Replies)
Discussion started by: vk39221
8 Replies

6. Shell Programming and Scripting

How to find empty files in a directory and write their file names in a text?

I need to find empty files in a directory and write them into a text file. Directory will contain old files as well, i need to get the empty files for the last one hour only. (1 Reply)
Discussion started by: vel4ever
1 Replies

7. Shell Programming and Scripting

Delete empty files from a directory entered in command prompt

My code to "Delete empty files from a directory entered in command promt" #/bin/sh echo "Enter directory" read gh for file in `ls $gh` do # to get the size of file a=$( ls -l file | awk ' {print $7} '); echo $a if then echo "removing file " rm file fi done (6 Replies)
Discussion started by: adirajup
6 Replies

8. UNIX for Dummies Questions & Answers

Exit Status Of Find Command

Hello All, I am trying to capture the exit status of find command and want to delete the files only when it is successful. But it is always returning me as success even if the pattern of that file doesn't exist in the current directory. please help, checked manual page but couldn't able to figure... (6 Replies)
Discussion started by: Ariean
6 Replies

9. Shell Programming and Scripting

Trapping the return status from FIND command

I have the following code in a script: find . \( ! -name . -prune \) -name "cg*" -exec cp -p {} "${temp_dir}" \; ret_stat=$? I think the return status is only captured for the 'find' command and not for the 'cp' command. Is there a way to get the return status for the 'cp' command... (7 Replies)
Discussion started by: vskr72
7 Replies

10. UNIX for Beginners Questions & Answers

Find command giving bad status error

In a fastload teradata utility I am trying to delete the files which are older than 30days using the find and rm command as following. find . -name 'xxx_*' -mtime +30 -exec rm -f {} \; I expect it to delete all the files older than 30 days but sometimes it gives an error : find: bad status--... (3 Replies)
Discussion started by: stelkar
3 Replies
SVN-BISECT(1)						      General Commands Manual						     SVN-BISECT(1)

NAME
svn-bisect - Bisect Subversion revisions to find a regression SYNOPSIS
svn-bisect start [good_rev [bad_rev]] svn-bisect {good|bad} [rev] svn-bisect run command svn-bisect reset svn-bisect status DESCRIPTION
svn-bisect helps to automate finding a bug or behavior change in a Subversion working copy. Given an initial "good" revision, with the desired or original behavior, and a newer "bad" revision, with the undesired or modified behavior, svn-bisect will do a binary search through the revision range to find which revision caused the change. svn-bisect must be initialized in a working copy, with svn-bisect start. It also needs to be given at least one good revision (the base- line) and one bad revision (known modified behavior) revision. Sub-commands: start Initializes or reinitializes svn-bisect; optionally takes good and bad revision parameters. good rev bad rev Tells svn-bisect that a revision is good or bad, defining or narrowing the search space. If not specified, revision defaults to the current revision in the working copy. svn-bisect will then update to a revision halfway between the new good and bad boundaries. If this update crosses a point where a branch was created, it switches in or out of the branch. reset Resets the working copy to the revision and branch where svn-bisect start was run. In the simple case this is equivalent to rm -r .svn-bisect; svn update, but not if it has crossed branches, and not if you did not start at the HEAD revision. In any case, svn-bisect never keeps track of mixed-revision working copies, so do not use svn-bisect in a working copy that will need to be restored to mixed revisions. status Prints a brief status message. run command Runs the bisection in a loop. You must have already defined initial good and bad boundary conditions. Each iteration through the loop runs command as a shell command (a single argument, quoted if necessary) on the chosen revision, then marks the revision as good or bad, based on the exit status of command. EXAMPLES
Assume you are trying to find which revision between 1250 and 1400 caused the make check command to fail. svn-bisect start 1250 1400 svn-bisect run 'make check' svn-bisect reset ENVIRONMENT
SVN The Subversion command-line program to call (default svn). FILES
.svn-bisect The directory containing state information, removed after a successful bisection. SEE ALSO
git-bisect(1). AUTHOR
Written by Robert Millan and Peter Samuelson, for the Debian Project (but may be used by others). 2009-10-22 SVN-BISECT(1)
All times are GMT -4. The time now is 01:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy