02-22-2007
Different results from awk, sed, tr in different directories???
I cannot explain why it gives different results when I try the awk, sed, tr command combination with the same input.
(aondufd1)psoftfs:/aon/dev/psoft/FSTST88/autosys>echo ${MailFile}
+ echo mfint003pr.in1*
mfint003pr.in1*
(aondufd1)psoftfs:/aon/dev/psoft/FSTST88/autosys/scripts>echo ${MailFile} | awk -F. '{ print $1 "." }' | sed 's/.*\(...\)\..*/\1/' | tr [A-Z] [a-z] | tr -d [0-9]
+ echo mfint003pr.in1*
+ awk -F. { print $1 "." }
+ sed s/.*\(...\)\..*/\1/
+ tr -d 1
+ tr [A-Z] a
3pr
(aondufd1)psoftfs:/aon/dev/psoft/FSTST88/autosys/scripts>cd ../parm
+ cd ../parm
(aondufd1)psoftfs:/aon/dev/psoft/FSTST88/autosys/parm>echo ${MailFile} | awk -F. '{ print $1 "." }' | sed 's/.*\(...\)\..*/\1/' | tr [A-Z] [a-z] | tr -d [0-9]
+ echo mfint003pr.in1*
+ awk -F. { print $1 "." }
+ sed s/.*\(...\)\..*/\1/
+ tr -d [0-9]
+ tr [A-Z] [a-z]
pr
One big question mark in my head right now. Could someone please help. Thanks.
There were no additional profiles loaded when changing directories. just doing the cd command.
The output should be 3pr. That would be the correct one, right?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there all,
I am using a line to get some replys from my PS
I do
ps -ef |awk '{printf $9}'
But my result is 1 big line.
No spaces between the lines or someting
for example:... (2 Replies)
Discussion started by: draco
2 Replies
2. UNIX for Dummies Questions & Answers
TIA,
I'm using FreeBSD 6
I have a series of Directories (A,B,C,...Z). Each directory has files and other directories within it.
I want to compress the contents of each top directory into a single file so that I get an archive of each directory (for example, A.gzip) AND and want to move... (5 Replies)
Discussion started by: jccbin
5 Replies
3. Shell Programming and Scripting
Hello,
I need help in creating a PERL script for parsing test result files to get the results (pass or fail). Each test case execution generates a directory with few files among which we are interested in .result file.
Lets say Testing is home directory. If i executed 2 test cases. It will... (4 Replies)
Discussion started by: ravi.videla
4 Replies
4. Shell Programming and Scripting
I use many different machines at work, each with different versions of o/s's and installed applications. Sed in vi is particularly inconvenient in the sense that sometimes it will accept the "\r" as a carriage return, sometimes not. Same thing with "\n". For instance, if I have a list of hosts... (7 Replies)
Discussion started by: MaindotC
7 Replies
5. Shell Programming and Scripting
Dear all,
How can I print results (and of course, send this result to the text file) of sed command.
I mean, I want to know which lines of which files sed command has found.
For e.g, the result text file should contains:
file1.c:line 12
file2.h:line 14
file2.h:line 37
Please help me (10 Replies)
Discussion started by: Hannibal2010
10 Replies
6. Shell Programming and Scripting
Hi,
Need help with a sed command that I am using to substitute 3 positions of a pipe delimited file.
i am getting different results while substituting the same position of two different files with the same value. Please see details below:
$ cat chk2
... (3 Replies)
Discussion started by: vmenon
3 Replies
7. Shell Programming and Scripting
I have been living with this problem with GNU sed v4.1.4 for a long time, but now I really need to figure it out.
When using a list in either an address or a search, the expression is matching lower and upper-case letters. works as it should.
For example, if I run
sed -nr "// p"... (7 Replies)
Discussion started by: nctrader
7 Replies
8. Shell Programming and Scripting
I created 3 files with the identical data as follows
dial-peer voice 9999 pots
trunkgroup CO
list outgoing Local
translation-profile outgoing LOCAL-7-DIGITS-NO-PREPEND-97
preference 2
shutdown
destination-pattern 9......$
forward-digits 7
dial-peer voice 10000 pots
... (6 Replies)
Discussion started by: popeye
6 Replies
9. Shell Programming and Scripting
find $SRC -type f -name *.emlx |
while read FILE
do
if :
then sed -n '/From/p' $FILE
fi
done > $DEST-output.txt
The loop above spits out a .txt file with several lines that look like this:
From: John Smith <jsmith@company.com>
How can I narrow that sed result to spit out the email... (5 Replies)
Discussion started by: sudo
5 Replies
10. Shell Programming and Scripting
I have one big file of size 9GB (big_file.txt). This big file has sentences and paragraphs like any usual English document. I have another file consisting of replacement strings for sed to use. The file name is replace.sed and each entry in one line looks like this:
s/\<shout\>/shout/g
s/\<b is... (2 Replies)
Discussion started by: shoaibjameel123
2 Replies
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)