I've tried both and I think the one that I more readily understand and has worked all OK is your contribution Don
Agma - apologies but didn't understand <source##*/>....the ##* bit but I did appreciate you taking the time to explain that I didn't need cat / while
Hi davidra,
I'm glad to hear that my contribution worked for you.
This is what ${source##*/} does: it looks at the shell variable named source and if its value matches the pattern */ (which matches any string that ends with a / character), it removes the longest match for that pattern from the start (left) of the string. If $source does not contain any / characters, it is expanded unchanged. Similarly, ${var#pattern} removes the shortest match for pattern from the start of the expansion of $var, ${var%pattern} removes the shortest match for pattern from the end of the expansion of $var, and ${var%%pattern} removes the longest match for pattern from the end of the expansion of $var. For example:
produces the output:
This User Gave Thanks to Don Cragun For This Post:
The Web-based contact form on my site has been under distributed spamming attacks for nearly a month already. Obviously, a spammer has tried to generate HTTP requests containing ads to male drugs and all sorts of similar stuff directly to the form mail processor script on my site using a robot, as... (5 Replies)
Hi,
I am using the following command to extract any log files that are older than 3 days using the following command.
find DIR/LOGDIR -type f -mtime +3 |grep LOG > log_list.out
The results are
DIR/LOGDIR/1.LOG
DIR/LOGDIR/2.LOG
DIR/LOGDIR/3.LOG
DIR/LOGDIR/4.LOG
How do inculde (basename... (4 Replies)
hi if we have to use basename how can we do this in awk?
did the below but is not working..
psg -t "?"| awk '{
command=($5 ~ /^/)? $9:$8
# cmd_name=`basename $command` (gives error)
system("basename $command >>... (10 Replies)
Hi Experts,
I am adding a column of numbers with awk , however not getting correct output:
# awk '{sum+=$1} END {print sum}' datafile
2.15291e+06
How can I getthe output like : 2152910
Thank you..
# awk '{sum+=$1} END {print sum}' datafile
2.15079e+06 (3 Replies)
I am having a hard time extracting the file name from the above code. Instead of printing /folder/file.1$.5$, I would like it to print the file name file.1$.5$.
I have tried using basename but it looks like NAWK or AWK does not recognise basename. Each time I type it in, it prints out the word... (4 Replies)
Hi gurus,
i need your advise on how to process this file using awk.
i have this file
COLA COLB COLC COLD COLE COLF COLG COLH
AAAA 86 111 122 133 144 155 266 377
BBBB 70 211 222 233 244 255 266 ... (6 Replies)
im trying to extract the basename of a process running on a host
processx is running at host1 as /applications/myapps/bin/processx
i wanted to check if its running, then extract the basename only using:
$ ssh host1 "ps aux | grep -v 'grep' | grep 'processx'" | awk '{ print basename $11}'
... (10 Replies)
Here is a very simple Korn shell script running on an AIX 5.3 box.
Why does this work without the $ prepended to RET_CD?
#!/bin/ksh
RET_CD=0
if &&
then
echo "RET_CD is not 0 and not 2"
else
echo "RET_CD is a 0 or a 2"
fi (3 Replies)
I'm using solaris 10
Scenario as follows
I have a logfile with 2 columns:
column 1 = source directory + filename
column 2 = destination directory + filename
Using cron, my script polls for new files and adds them to the logfile ($ELOG) as described above. Using sed, the distination... (2 Replies)
Hi Guru's.
I am trying to use to check if $5 is greater than 80 & if not 100, then to print $0 :
awk '{ if ($5>80) && if ($5 != 100) print $0}
But getting error:
>bdf1|sed 's/%//g'|awk '{ if ($5>80) && if ($5 != 100) print $0}'
syntax error The source line is 1.
The error... (6 Replies)
Discussion started by: rveri
6 Replies
LEARN ABOUT NETBSD
glob
GLOB(7) BSD Miscellaneous Information Manual GLOB(7)NAME
glob -- shell-style pattern matching
DESCRIPTION
Globbing characters (wildcards) are special characters used to perform pattern matching of pathnames and command arguments in the csh(1),
ksh(1), and sh(1) shells as well as the C library functions fnmatch(3) and glob(3). A glob pattern is a word containing one or more unquoted
'?' or '*' characters, or ``[..]'' sequences.
Globs should not be confused with the more powerful regular expressions used by programs such as grep(1). While there is some overlap in the
special characters used in regular expressions and globs, their meaning is different.
The pattern elements have the following meaning:
? Matches any single character.
* Matches any sequence of zero or more characters.
[..] Matches any of the characters inside the brackets. Ranges of characters can be specified by separating two characters by a '-' (e.g.
``[a0-9]'' matches the letter 'a' or any digit). In order to represent itself, a '-' must either be quoted or the first or last
character in the character list. Similarly, a ']' must be quoted or the first character in the list if it is to represent itself
instead of the end of the list. Also, a '!' appearing at the start of the list has special meaning (see below), so to represent
itself it must be quoted or appear later in the list.
Within a bracket expression, the name of a character class enclosed in '[:' and ':]' stands for the list of all characters belonging
to that class. Supported character classes:
alnum cntrl lower space
alpha digit print upper
blank graph punct xdigit
These match characters using the macros specified in ctype(3). A character class may not be used as an endpoint of a range.
[!..] Like [..], except it matches any character not inside the brackets.
Matches the character following it verbatim. This is useful to quote the special characters '?', '*', '[', and '' such that they
lose their special meaning. For example, the pattern ``\*[x]?'' matches the string ``*[x]?''.
Note that when matching a pathname, the path separator '/', is not matched by a '?', or '*', character or by a ``[..]'' sequence. Thus,
/usr/*/*/X11 would match /usr/X11R6/lib/X11 and /usr/X11R6/include/X11 while /usr/*/X11 would not match either. Likewise, /usr/*/bin would
match /usr/local/bin but not /usr/bin.
SEE ALSO fnmatch(3), glob(3), re_format(7)HISTORY
In early versions of UNIX, the shell did not do pattern expansion itself. A dedicated program, /etc/glob, was used to perform the expansion
and pass the results to a command. In Version 7 AT&T UNIX, with the introduction of the Bourne shell, this functionality was incorporated
into the shell itself.
BSD November 30, 2010 BSD