05-21-2003
This is even better:
$ echo "Attempting to contact (ADDRESS=(PROTOCOL=TCP)(Host=chamar)(Port=1541))"
|tr -d ")" | cut -d"=" -f5
Should've thought of this the first time.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Does anybody know how do we parse a file (ex. SIF file) into a delimited text file in UNIX? (7 Replies)
Discussion started by: nguda
7 Replies
2. UNIX for Advanced & Expert Users
hi,:)
onsider the followinf two lines
J="$(scriptbc -p 8 $I / \(12 \* 100 \) )"
N="$(( $L * 12 ))"
In the first line I put \ before * like \* and its working fine.
But in the second line if put \ before * i am getting parse error.
What might be the reason?Any idea pls.
cheers
RRK (1 Reply)
Discussion started by: ravi raj kumar
1 Replies
3. Shell Programming and Scripting
# Start
"ABC" SFFd 0 4
Time SFFT 4 8 {Sec}
User SFFTimeVal 12 8 {Sec}
# Start
"CP" SFFT ... (3 Replies)
Discussion started by: navsharan
3 Replies
4. Shell Programming and Scripting
I need a script that will always return an engine of table, which not
depends on the table structure.
I need it to be done exactly from the "show create table ..." statement.
If there is a easiest way, except "show table status", please write.
mysql -u root db -sBe "show create table... (1 Reply)
Discussion started by: mirusnet
1 Replies
5. Shell Programming and Scripting
Hi
I'm writing simple perl script to parse the ftp log as below:
Local directory now /home/user/testing
227 Entering Passive Mode (192,254,19,34,8,228).
125 Data connection already open; Transfer starting.
09-25-09 02:33PM 25333629 abc.tar
09-14-09 12:50PM 18015752... (1 Reply)
Discussion started by: netxus
1 Replies
6. Shell Programming and Scripting
On the command, when I type in certain commands, they will display a prompt waiting for some input. When I type in the requested input, it will display the info I requested.
For example, if I enter the telnet command, it will display a telnet prompt and wait for me to enter something.
I... (1 Reply)
Discussion started by: april
1 Replies
7. Shell Programming and Scripting
Hi,
I have a really simple question...I think. I want to be able to parse two or more files into one by reading the first record from each file into new file then go back to the first file and start reading the second record in from each file into new file and so on. I am new to using awk and am... (5 Replies)
Discussion started by: qray2011
5 Replies
8. Shell Programming and Scripting
Attached file is parsed so that only the three columns result.
DACH1 occurs 34 times with an average of 0.881541
NEB occurs 159 times with an average of 0.837628
LTBP1 occurs 46 times with an average of 0.748722
parse result: output.txt (the text is removed and the xxx is seperated in a... (6 Replies)
Discussion started by: cmccabe
6 Replies
9. Shell Programming and Scripting
I downloaded source code using:
wget -qO- http://fulgentdiagnostics.com/test/clinical-exome/ | cat > flugentsource.txt
Now I am trying to use sed to parse it to confirm a gene count. Basically, output (flugent.txt) all the gene names with a total count after them
I'm not all that... (5 Replies)
Discussion started by: cmccabe
5 Replies
10. Programming
I am trying to parse a string using SQL but am too new and still learning. I have text in a control or field 685 that is variable, but always the same format.
field 685 input
arr 2q33.3q34(200,900,700-209,000,000)x2 xxx
Desired output
2:200900700-209000000
Basically, the # after the... (2 Replies)
Discussion started by: cmccabe
2 Replies
LEARN ABOUT FREEBSD
getopt
GETOPT(1) BSD General Commands Manual GETOPT(1)
NAME
getopt -- parse command options
SYNOPSIS
args=`getopt optstring $*` ; errcode=$?; set -- $args
DESCRIPTION
The getopt utility is used to break up options in command lines for easy parsing by shell procedures, and to check for legal options.
Optstring is a string of recognized option letters (see getopt(3)); if a letter is followed by a colon, the option is expected to have an
argument which may or may not be separated from it by white space. The special option '--' is used to delimit the end of the options. The
getopt utility will place '--' in the arguments at the end of the options, or recognize it if used explicitly. The shell arguments ($1 $2
...) are reset so that each option is preceded by a '-' and in its own shell argument; each option argument is also in its own shell argu-
ment.
EXIT STATUS
The getopt utility prints an error message on the standard error output and exits with status > 0 when it encounters an option letter not
included in optstring.
EXAMPLES
The following code fragment shows how one might process the arguments for a command that can take the options -a and -b, and the option -o,
which requires an argument.
args=`getopt abo: $*`
# you should not use `getopt abo: "$@"` since that would parse
# the arguments differently from what the set command below does.
if [ $? -ne 0 ]; then
echo 'Usage: ...'
exit 2
fi
set -- $args
# You cannot use the set command with a backquoted getopt directly,
# since the exit code from getopt would be shadowed by those of set,
# which is zero by definition.
while true; do
case "$1" in
-a|-b)
echo "flag $1 set"; sflags="${1#-}$sflags"
shift
;;
-o)
echo "oarg is '$2'"; oarg="$2"
shift; shift
;;
--)
shift; break
;;
esac
done
echo "single-char flags: '$sflags'"
echo "oarg is '$oarg'"
This code will accept any of the following as equivalent:
cmd -aoarg file file
cmd -a -o arg file file
cmd -oarg -a file file
cmd -a -oarg -- file file
SEE ALSO
getopts(1), sh(1), getopt(3)
HISTORY
Written by Henry Spencer, working from a Bell Labs manual page. Behavior believed identical to the Bell version. Example changed in FreeBSD
version 3.2 and 4.0.
BUGS
Whatever getopt(3) has.
Arguments containing white space or embedded shell metacharacters generally will not survive intact; this looks easy to fix but is not. Peo-
ple trying to fix getopt or the example in this manpage should check the history of this file in FreeBSD.
The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of
getopt; this again is hard to fix.
The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell ver-
sion to another.
Each shellscript has to carry complex code to parse arguments halfway correctly (like the example presented here). A better getopt-like tool
would move much of the complexity into the tool and keep the client shell scripts simpler.
BSD
January 26, 2011 BSD