Very nice radoulov! I'm a bash dude and was familiar with ${VAR/MATCH/REPLACE/} syntax but didn't know about all the extra details, so was a bit confused at first. For anyone else that's looking for an explanation, here's the relevant bit from bash's man page:
PS: Can you explain what exactly "IFS=" is doing in there?
Hello,
I have a requirement to search a directory, which contains any number of other directories for file names that contain special characters.
directory structure
DIR__
|__>DIR1
|__>DIR2__
|__>DIR2.1
|__>DIR2.2
|__>DIR3
..
... (8 Replies)
Hi.
I have many files in a folder, and even more in the subfolders. I need a script that finds and removes certain characters (them being /n in this one) in the files in the folder and it's subfolders.
So, could someone write me a script that works in Linux, does this:
Searchs for "/n" in... (5 Replies)
Hi all,
Am creating files and doing copy,compare and deletion.
As i do not want to mention the filepath everywhere, i store the filepaths in variables.
FILENAME="/home/test/create/Myfile.txt"
WR_PATH="/home/test/wrie/writefile.txt"
RD_PATH="/home/test/myread/readfile.txt"
echo "This is my... (2 Replies)
I want to create a temp file which is named based on a search string. The search string may contain spaces or characters that aren't supposed to be used in filenames so I want to strip those out.
My thought was to use 'tr' with but the result is the opposite of what I want:
$ echo "test... (5 Replies)
Hi Gurus,
Do any kind souls encounter have the same script as mentioned here.
Find and compare filenames in different mount point and remove duplicates.
Thanks a million!!!
wanna13e (7 Replies)
Hi,
I am creating a script to do a find and replace single/multiple lines in a file with any number of lines.
I have written a logic in a script that reads a reference file say "findrep" and populates two variables $FIND and $REPLACE
print $FIND gives
Hi How r $u
Rahul()
Note:... (0 Replies)
I have a perl find program that will find all files of window application stored on unix disks.
Ofcourse these files contain all the weird characters windows allows, but on *nix pukes out all kinds of unwanted effects when processing these.
Is their a utility that will escape all these... (3 Replies)
hello,
I'm trying to figure out which tool is best for recursively renaming and files or folders using the characters \/*?”<>| in their name. I've tried many examples that use Bash, Python and Perl, but I'm not much of a programmer I seem to have hit a roadblock.
Does anyone have any... (15 Replies)
Hi,
I have a file having following content.
<sip:9376507346@97.208.31.7:51088
<sip:9907472291@97.208.31.7:51208
<sip:8103742422@97.208.31.7:51024
<sip:9579892841@97.208.31.7:51080
<sip:9370904222@97.208.31.7:51104
<sip:9327665215@97.208.31.7:51104
<sip:9098364262@97.208.31.7:51024... (2 Replies)
Hi Guys,
My requirement is to remove any invisible and special characters from the file like control M(carriage return) and alt numerics and it should not replace @#!$%
abc|xyz|acd¥£ó
adc|123| 12áí
Please help on this.
Thanks
Rakesh (1 Reply)
Discussion started by: rakeshp
1 Replies
LEARN ABOUT BSD
find
FIND(1) General Commands Manual FIND(1)NAME
find - find files
SYNOPSIS
find pathname-list expression
find pattern
DESCRIPTION
In the first form above, find recursively descends the directory hierarchy for each pathname in the pathname-list (i.e., one or more path-
names) seeking files that match a boolean expression written in the primaries given below. In the descriptions, the argument n is used as
a decimal integer where +n means more than n, -n means less than n and n means exactly n.
The second form rapidly searches a database for all pathnames which match pattern. Usually the database is recomputed weekly and contains
the pathnames of all files which are publicly accessible. If escaped, normal shell "globbing" characters (`*', `?', `[', and ']') may be
used in pattern, but the matching differs in that no characters (e.g. `/') have to be matched explicitly. As a special case, a simple pat-
tern containing no globbing characters is matched as though it were *pattern*; if any globbing character appears there are no implicit
globbing characters.
-name filename
True if the filename argument matches the current file name. Normal shell argument syntax may be used if escaped (watch out for
`[', `?' and `*').
-perm onum
True if the file permission flags exactly match the octal number onum (see chmod(1)). If onum is prefixed by a minus sign, more
flag bits (017777, see stat(2)) become significant and the flags are compared: (flags&onum)==onum.
-type c True if the type of the file is c, where c is b, c, d, f, l or s for block special file, character special file, directory, plain
file, symbolic link, or socket.
-links n True if the file has n links.
-user uname
True if the file belongs to the user uname (login name or numeric user ID).
-nouser True if the file belongs to a user not in the /etc/passwd database.
-group gname
True if the file belongs to group gname (group name or numeric group ID).
-nogroup True if the file belongs to a group not in the /etc/group database.
-size n True if the file is n blocks long (512 bytes per block).
-inum n True if the file has inode number n.
-atime n True if the file has been accessed in n days.
-mtime n True if the file has been modified in n days.
-exec command
True if the executed command returns a zero value as exit status. The end of the command must be punctuated by an escaped semi-
colon. A command argument `{}' is replaced by the current pathname.
-ok command
Like -exec except that the generated command is written on the standard output, then the standard input is read and the command
executed only upon response y.
-print Always true; causes the current pathname to be printed.
-ls Always true; causes current pathname to be printed together with its associated statistics. These include (respectively) inode
number, size in kilobytes (1024 bytes), protection mode, number of hard links, user, group, size in bytes, and modification time.
If the file is a special file the size field will instead contain the major and minor device numbers. If the file is a symbolic
link the pathname of the linked-to file is printed preceded by ``->''. The format is identical to that of ``ls -gilds'' (note
however that formatting is done internally, without executing the ls program).
-newer file
True if the current file has been modified more recently than the argument file.
-cpio file
Write the current file on the argument file in cpio format.
-xdev Always true; causes find not to traverse down into a file system different from the one on which current argument pathname
resides.
The primaries may be combined using the following operators (in order of decreasing precedence):
1) A parenthesized group of primaries and operators (parentheses are special to the Shell and must be escaped).
2) The negation of a primary (`!' is the unary not operator).
3) Concatenation of primaries (the and operation is implied by the juxtaposition of two primaries).
4) Alternation of primaries (`-o' is the or operator).
EXAMPLES
To find all accessible files whose pathname contains `find':
find find
To typeset all variants of manual pages for `ls':
vtroff -man `find '*man*/ls.?'`
To remove all files named `a.out' or `*.o' that have not been accessed for a week:
find / ( -name a.out -o -name '*.o' ) -atime +7 -exec rm {} ;
FILES
/etc/passwd
/etc/group
/var/db/find.codes coded pathnames database
SEE ALSO sh(1), test(1), fs(5)
Relevant paper in February, 1983 issue of ;login:.
BUGS
The first form's syntax is painful, and the second form's exact semantics is confusing and can vary from site to site.
More than one `-newer' option does not work properly.
7th Edition October 11, 1996 FIND(1)