11-04-2013
Your 1. mistake is two nested loops: find (that loops thru the files) within a for loop.
Your 2. mistake: find's exit status is independent of found files. if find ... is nonsense unless output is tested (e.g. with test or grep command).
Your 3. probable mistake: if two or more files in a directory match one condition, the mv to a common file will replace i.e. lose the previous files.
Last edited by MadeInGermany; 11-04-2013 at 09:27 PM..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
HI All,
I am having a bit of trouble using the find command in my shell (korn) script.
I was hoping someone could help me.
I am trying to build up a dynamic find command based on some parameters.
When I execute the command I get the following error:
find: incomplete statement
I have... (6 Replies)
Discussion started by: sethkor
6 Replies
2. Shell Programming and Scripting
Hi all,
Have the following snippet of code that I'm having trouble trying to work ...
The snippet of code is running on our Production Server and the intent is to copy the second most recent IDE file across from the Development Server.
I have the following files defined in $DEVLOC ...... (4 Replies)
Discussion started by: Cameron
4 Replies
3. Shell Programming and Scripting
Hi,
Iam having a strange problem, wandering if soneone can throw some lights.
I have statement
find . -maxdepth 1 -name 'File1*.tsv' -mtime +1 -print
I expect the above statement to print the files older than 1 day or 24 hrs,
however it doesn't work that way. When issue above command,... (2 Replies)
Discussion started by: braindrain
2 Replies
4. UNIX for Dummies Questions & Answers
When I am doing the first command the result shows all the files, links, directories except the ones that contain the word logs
find . -type f -o -type l -o -type d | grep -v logs
But when I am trying to do this even the logs are getting tarred
tar -cvf fdtvision.tar `find . -type f -o -type l... (2 Replies)
Discussion started by: venu_nbk
2 Replies
5. UNIX for Dummies Questions & Answers
I am using HP-UNIX , The below command doesnt display anything although i have changed a file in the directory by
toutch -t 200010101800 nfile
find /tmp/transfer/ -name "*.*" -mtime +1
Any problrm with the find command i written . .Please help ??..
Thanks,
Arun (4 Replies)
Discussion started by: arunkumar_mca
4 Replies
6. Shell Programming and Scripting
Hi All,
I am using following find command to delete the records older than 7 days but getting missing conjuction error.Kindly suggest:
The command is:
find <complete_dir_path> \(! -name usr -prune \) -type f -name "*.txt" -mtime +6 -print | xargs rm (11 Replies)
Discussion started by: visingha
11 Replies
7. Shell Programming and Scripting
I'm trying to display the full file name (including the full path) and file size of all files whose name (excluding the path) is longer than 10 characters.
I came up with find path -type f -name ".{10, }" -printf "%s %p\n", but I'm getting a "find: path: No such file or directory". What's wrong... (2 Replies)
Discussion started by: raidkridley
2 Replies
8. Shell Programming and Scripting
for index in `find /root -name *.jar | grep "/lib"`; do echo "$index"; done
sometimes its throwing error saying
find: paths must precede expression
Usage: find
some1 suggested me that :
Code:
for index in `find /technologies -name '*.jar' | grep "/lib"`
do
echo "$index"... (2 Replies)
Discussion started by: crackthehit007
2 Replies
9. Shell Programming and Scripting
Hi
I want to find files with size +10000M and specified directorys except
when i use more than one `-name` acton is fail
I try -a (and) and -o (-or) but results fail :(
find . \( -name ./oracle* -prune -o -name "*arc*" -prune -o -name "*oracle*" -prune -o -size +10000k \) -exec ls -lh {}... (7 Replies)
Discussion started by: ygemici
7 Replies
10. Shell Programming and Scripting
Hello Guys ,
I am trying to run below find command in one of my SH script on a HP UX machine.
find /tmp -type f -name "MGCA*.log" -prune -exec rm -f {} \; 2>&1
I want this to check my tmp directory and delete MGCA log files .But below error message is printed on Promt :-
find: cannot... (2 Replies)
Discussion started by: himanshu sood
2 Replies
LEARN ABOUT REDHAT
sane-find-scanner
sane-find-scanner(1) General Commands Manual sane-find-scanner(1)
NAME
sane-find-scanner - find SCSI and USB scanners and their device files
SYNOPSIS
sane-find-scanner [-h|-?] [-v] [-q] [-f] [devname]
DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and some USB scanners and determine their Unix device files. It's part of the sane-
backends package.
For SCSI scanners, it checks the default generic SCSI device files (e.g., /dev/sg0) and /dev/scanner. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "processor" (some old HP scanners seem to send "processor"). So sane-find-
scanner will find any SCSI scanner connected to those default device files even if it isn't supported by any SANE backend.
For USB scanners, first the USB kernel scanner device files (e.g. /dev/usb/scanner0), /dev/usb/scanner, and /dev/usbscanner are tested. The
files are opened and the vendor and device ids are determined if the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module or the FreeBSD or OpenBSD uscanner driver. After that test, sane-
find-scanner tries to scan for USB devices found by the USB library libusb (if available). There is no special USB class for scanners, so
the heuristics used to distinguish scanners from other USB devices is not perfect. sane-find-scanner will even find USB scanners, that are
not supported by any SANE backend.
sane-find-scanner won't find parallel port scanners, or scanners connected to proprietary ports.
OPTIONS
-h, -? Prints a short usage message.
-v Verbose output. If used once, sane-find-scanner shows every device name and the test result. If used twice, SCSI inquiry informa-
tion and the USB device descriptors are also printed.
-q Be quiet. Print only the devices, no comments.
-f Force opening all explicitely given devices as SCSI and USB devices. That's useful if sane-find-scanner is wrong in determing the
device type.
devname Test device file "devname". No other devices are checked if devname is given.
EXAMPLE
sane-find-scanner -v
Check all SCSI and USB devices for available scanners and print a line for every device file.
sane-find-scanner /dev/scanner
Look for a (SCSI) scanner only at /dev/scanner and print the result.
SEE ALSO
sane(7), sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1), sane-"backendname"(5)
AUTHOR
Oliver Rauch, Henning Meier-Geinitz and others
SUPPORTED PLATFORMS
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel, libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the vendor
and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris, FreeBSD, NetBSD, OpenBSD, and HP-UX.
BUGS
No support for parallel port scanners yet.
15 Sep 2002 sane-find-scanner(1)