Sponsored Content
Top Forums Shell Programming and Scripting "find command" to find the files in the current directories but not in the "subdir" Post 302217144 by vijayq8 on Tuesday 22nd of July 2008 04:01:00 AM
Old 07-22-2008
MySQL

Quote:
Originally Posted by cooldude
Vijay, that does not work if a sub directory name contains a ".". You may think that's uncommon, but the first time I tried your command, it failed because the directory I was in had a period!
Hi,
it should work man, i tried in my unix box then only i posted the reply. see my result.

[mipl@subversion ~]$ ls
coding dead.letter s2.sh scripting sname sorted_names test test1 vijay
[mipl@subversion ~]$ ls -a
. .bash_profile dead.letter .kde sorted_names .viminfo
.. .bashrc .emacs s2.sh test .xemacs
.bash_history .canna .emacs.d scripting test1 .zshrc
.bash_logout coding .gtkrc sname vijay
[mipl@subversion ~]$ find *.*
dead.letter
s2.sh
[mipl@subversion ~]$

Hope you clear now.

Thanks & Regards
Vijay.Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

chmod 777 on all directories below...how do I do that using the "find" command?

I've got 100 directories that each have 2 directories with in them. Structered like this: /home/domains/domain1/ through to /home/domains/domain100/ and those 2 directories mentioned above are here: /home/domains/domain1/directory1/ /home/domains/domain1/directory2/ through to... (7 Replies)
Discussion started by: Neko
7 Replies

2. UNIX for Dummies Questions & Answers

Listing only directories in the current working directory using the "ls" command

Hello All, I am trying to list only directories in my current directory using the command "ls -d". But the output only contains the default directory "." and doesn't list the rest of the directories in the working directory. Can anyone explain why this is happening (2 Replies)
Discussion started by: igandu
2 Replies

3. Shell Programming and Scripting

grep to find content in between curly braces, "{" and "},"

problem String ~~~~~~~~~~~~~~~~~~ icecream= { smart peopleLink "good" LC "happy" , smartpeopleLink "dull" LC "sad" } aend = {smart vc4 eatr kalu} output needed ~~~~~~~~~~~~~~~~~~ smart peopleLink "good" LC "happy" , smartpeopleLink "dull" LC "sad" smart vc4... (4 Replies)
Discussion started by: keshav_rk
4 Replies

4. Shell Programming and Scripting

awk command to replace ";" with "|" and ""|" at diferent places in line of file

Hi, I have line in input file as below: 3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL My expected output for line in the file must be : "1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL" Can someone... (7 Replies)
Discussion started by: shis100
7 Replies

5. Shell Programming and Scripting

Problem with "find" and "grep" command

I want to list all files/lines which except those which contain the pattern ' /proc/' OR ' /sys/' (mind the leading blank). In a first approach I coded: find / -exec ls -ld {} | grep -v ' /proc/| /sys/' \; > /tmp/list.txt But this doesn't work. I got an error (under Ubuntu): grep:... (5 Replies)
Discussion started by: pstein
5 Replies

6. Shell Programming and Scripting

"find . -printf" without prepended "." path? Getting path to current working directory?

If I enter (simplified): find . -printf "%p\n" then all files in the output are prepended by a "." like ./local/share/test23.log How can achieve that a.) the leading "./" is omitted and/or b.) the full path to the current directory is inserted (enclosed by brackets and a blank)... (1 Reply)
Discussion started by: pstein
1 Replies

7. Shell Programming and Scripting

Find lines with "A" then change "E" to "X" same line

I have a bunch of random character lines like ABCEDFG. I want to find all lines with "A" and then change any "E" to "X" in the same line. ALL lines with "A" will have an "X" somewhere in it. I have tried sed awk and vi editor. I get close, not quite there. I know someone has already solved this... (10 Replies)
Discussion started by: nightwatchrenba
10 Replies

8. UNIX for Dummies Questions & Answers

Using "mailx" command to read "to" and "cc" email addreses from input file

How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address and column 3 contains “cc” e-mail address to include with same email. Sample input file, email.txt Below is an sample code where... (2 Replies)
Discussion started by: asjaiswal
2 Replies

9. Shell Programming and Scripting

find . -path "*_nobackup*" -prune -iname "*.PDF" \( ! -name "*_nobackup.*" \)

These three finds worked as expected: $ find . -iname "*.PDF" $ find . -iname "*.PDF" \( ! -name "*_nobackup.*" \) $ find . -path "*_nobackup*" -prune -iname "*.PDF" They all returned the match: ./folder/file.pdf :b: This find returned no matches: $ find . -path "*_nobackup*" -prune... (3 Replies)
Discussion started by: wolfv
3 Replies

10. Shell Programming and Scripting

find files in sub dir with tag & add "." at the beginning [tag -f "Note" . | xargs -0 {} mv {} .{}]

I am trying find files in sub dir with certain tags using tag command, and add the period to the beginning. I can't use chflags hidden {} cause it doesn't add period to the beginning of the string for web purpose. So far with my knowledge, I only know mdfind or tag can be used to search files with... (6 Replies)
Discussion started by: Nexeu
6 Replies
cd(1)							      General Commands Manual							     cd(1)

NAME
cd - change working directory SYNOPSIS
[directory] DESCRIPTION
If directory is not specified, the value of shell parameter is used as the new working directory. If directory specifies a complete path starting with or directory becomes the new working directory. If neither case applies, tries to find the designated directory relative to one of the paths specified by the shell variable. has the same syntax as, and similar semantics to, the shell variable. must have execute (search) permission in directory. exists only as a shell built-in command because a new process is created whenever a command is executed, making useless if written and pro- cessed as a normal system command. Moreover, different shells provide different implementations of as a built-in utility. Features of as described here may not be supported by all the shells. Refer to individual shell manual entries for differences. If is called in a subshell or a separate utility execution environment such as: (which invokes on accessible directories) does not affect the current directory of the caller's environment. Another usage of as a stand- alone command is to obtain the exit status of the command. EXTERNAL INFLUENCES
International Code Set Support Single- and multi-byte character code sets are supported. Environment Variables The following environment variables affect the execution of The name of the home directory, used when no directory operand is specified. A colon-separated list of pathnames that refer to directories. If the directory operand does not begin with a slash character, and the first component is not dot or dot-dot, searches for directory relative to each directory named in the variable, in the order listed. The new working directory is set to the first matching directory found. An empty string in place of a directory pathname represents the current direc- tory. If is not set, it is treated as if it was an empty string. EXAMPLES
Change the current working directory to the directory from any location in the file system: Change to new current working directory residing in the current directory: or Change to directory residing in the current directory's parent directory: Change to the directory whose absolute pathname is Change to the directory relative to home directory: RETURN VALUE
Upon completion, exits with one of the following values: The directory was successfully changed. An error occurred. The working directory remains unchanged. SEE ALSO
csh(1), pwd(1), ksh(1), sh-posix(1), sh(1), chdir(2). STANDARDS CONFORMANCE
cd(1)
All times are GMT -4. The time now is 02:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy