Use double bracket, and no quotes round wild cards. The double brackets are interpreted by Bash (or Kshell if using ksh) and they both interpret the right hand side of the expression as a pattern:
I'm trying to figure out how to build a small shell script that will find old .shtml files in every /tgp/ directory on the server and delete them if they are older than 10 days...
The structure of the paths are like this:
/home/domains/www.domain2.com/tgp/
/home/domains/www.domain3.com/tgp/... (1 Reply)
what will the cmd below do?
ls *.3
1 members mentions that to seek all permutations and combinations of the mp3 extension ill have to use curly braces, {} and not, .
what then will do? (13 Replies)
Just a quick question:
if I want to do a comparison with a wildcard in a shell script, do i just use '*'? Heres what I have:
elif ; then
continue
but that doesnt evaluate right. It tries to compare against the literal '/apps*' instead of anything that begins with '/apps' (2 Replies)
Hi, I have this code to search all "cif" files using wildcard
for file in *.cif
do
grep "Uiso" $file | awk '{ print $3, $4, $5 }' > tet
done
I get this error
"grep: *.cif: No such file or directory"
Please where am I going wrong!!!
Thank you in advance (6 Replies)
Can someone please explain the wildcards in this. How is this recursive? When I put this in my terminal it recursively displayed everything.
ls .* * (6 Replies)
Hi,
Can anyone help me how to use * in if statement.
File contains below
line1:a|b|c|Apple-RED|
line2:c|d|e|Apple-Green|
line3:f|g|h|Orange|
I need to find line by line 4th field contains 'Apple' or not.
Please help me at the earliest. (6 Replies)
i have got heaps of files (.pdf, .txt and .doc) files in one folder, i am making a program in PERL that helps me find the files i want easier using shell wildcard,
something like this!!
print "Enter a pattern: (must be in )";
$input = <STDIN>;
if (The input is in and valid wildcard... (3 Replies)
Hello,
I apologize for asking what is probably a simple question but I have been unable to understand the other posts on the topic. I have a file that has the following several lines:
ABC DEF GH:IJKLMNOP_QRS_TUV_11112012_ABCL5
ABC DEF GH:IJKLMNOP_QRS_TUV_11112013_ABCL4
ABC DEF... (4 Replies)
Hi Experts,
I want to use ls in the below form:
ls -l *.{txt,TXT} (working fine)
but when i am declaring a variable,
VAR="*.{txt,TXT}"
ls -l $VAR is not working. Please help.
Thanks. (4 Replies)
CD_numb is AM017
this code:
set the_Firstcom_CD to (do shell script "ls -d '/volumes/audioNAS/Firstcom/Access Music/' ") & CD_numb
gives me this:
"/volumes/audioNAS/Firstcom/Access Music/AM017"
the item I am looking for is AM017Q.
I can get the "*" syntax right so it never finder... (7 Replies)
Discussion started by: sbrady
7 Replies
LEARN ABOUT SUNOS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS -n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.10 3 Aug 1994 echo(1B)