Parsing OSX UNIX command results which print in multiple lines

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

String parsing help across multiple UNIX platforms

Need to parse XML like strings from a file. Using `egrep -A 1 "Panel Temp" "$2" | tail -2` I get the following string: <parameter name="Panel Temp" unit="0.1 C"> <value size="1" starttime="06-08-2017 09:36:56.968">95</value> I want to output: {"Panel Temp" 9.5 C} The 9.5 C is the value...

2. Shell Programming and Scripting

How to print different multiple lines after two patterns?

Hello, I need to print some lines as explained below, TXT example 1111 2222 3333 4444 5555 6666 7777 8888 6666 9999 1111 2222 3333 4444 5555

3. Shell Programming and Scripting

Print multiple lines on one line

Hi All, I have a file looks like: rst:singh:99.0.20-X86 2 rst:ACSI_SIN_SERVICES rst:singh:99.0.20-X86 2 rst:ACSI_BISI want to wrap 3rd col in one line and add variable value at start and ending of line and I wrote command: cat file | awk '{print $3}' | xargs > command.txt sed -e...

4. Shell Programming and Scripting

Print the first line for each multiple lines

Hi all, i need help to extract each first line from multiple lines occurrences based on different patterns (name) starting from the fourth lines like follows:- // header 1 header 2 header 3 // no acc name score rank //...

5. UNIX for Dummies Questions & Answers

How to print results from two lines using awk?

I need to print a specific string from an html file that's always occurring between two other known strings. Example: from the text below, I would like to print the bolded part: <this is a lot of text before the string I want to print> fullpath: abc/def/ghi/example.xlf -cfver. <sample text...

6. Shell Programming and Scripting

Multiple command execution inside awk command during xml parsing

below is the output xml string from some other command and i will be parsing it using awk cat /tmp/alerts.xml <Alert id="10102" name="APP-DS-ds_ha-140018-componentFailure-S" alertDefinitionId="13982" resourceId="11427" ctime="1359453507621" fixed="false" reason="If Event/Log Level(ANY) and...

7. Shell Programming and Scripting

print first few lines, then apply regex on a specific column to print results.

abc.dat tty cpu tin tout us sy wt id 0 0 7 3 19 71 extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 133.2 0.0 682.9 0.0 1.0 0.0 7.2 0 79 c1t0d0 0.2 180.4 0.1 5471.2 3.0 2.8 16.4 15.6 15 52 aaaaaa1-xx I want to skip first 5 line...

8. Shell Programming and Scripting

Logfile parsing with variable, multiple criterias among multiple lines

Hi all I've been working on a bash script parsing through debug/trace files and extracting all lines that relate to some search string. So far, it works pretty well. However, I am challenged by one requirement that is still open. What I want to do: 1) parse through a file and identify all...

9. Shell Programming and Scripting

print multiple lines using the grep command.

Hi All, Please find my piece of code below. I am trying to grep the word SUCCESS from $LOGFILE and storing in the grepvar variable. And i am placing that variable in a file. Now if i open the file, i can see the four lines but not in seperate four line s but in a paragraph. If am mailing that log...

10. Shell Programming and Scripting

(sed) parsing insert statement column that crosses multiple lines

I have a file with a set of insert statements some of which have a single column value that crosses multiple lines causing the statement to fail in sql*plue. Can someone help me with a sed script to replace the new lines with chr(10)? here is an example: insert into mytable(id, field1, field2)...

LEARN ABOUT OSX

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.

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 [ $? != 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.
	   for i
	   do
		   case "$i"
		   in
			   -a|-b)
				   echo flag $i set; sflags="${i#-}$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

     sh(1), getopt(3)

DIAGNOSTICS

     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.

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 isn't. 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 correcty (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
								   April 3, 1999							       BSD

Shell Programming and Scripting