Sponsored Content
Top Forums Shell Programming and Scripting Parsing a mixed format (flatfile+xml) logfile Post 302725159 by goddevil on Thursday 1st of November 2012 06:30:38 PM
Old 11-01-2012
Quote:
Originally Posted by Corona688
There are no ~'s in your data.

I can't make something which works for your data if you don't post a representative sample. I can try, but it's a game of blind man's bluff.
It was more of a general question and not specific to my example. I was playing around with the script to make the output better and it occurred me to replace the blanks with ~ and then use it as an FS. Then i got to wondering if i can use regexp for the substution range in the sed command.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

parsing xml

I want to use wget comment to parse an xml parse that exist in an online website. How can I connect it using shell script through Unix and how can I parse it?? (1 Reply)
Discussion started by: walnut
1 Replies

2. 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... (3 Replies)
Discussion started by: reminder
3 Replies

3. Shell Programming and Scripting

logfile parsing

I thought I was pretty handy with awk until I got this one. :) I'm trying to parse a log file where the events could have different delimiters (2 scripts is ok), the errors are spread over multiple lines, and I"m trying to figure out how to not read the same lines that have already been read. ... (1 Reply)
Discussion started by: linkslice
1 Replies

4. Shell Programming and Scripting

XML parsing

I have a xml file attached. I need to parse parameterId and its value My output should be like 151515 38 151522 32769 and so on.. Please help me. Its urgent (6 Replies)
Discussion started by: LavanyaP
6 Replies

5. UNIX for Advanced & Expert Users

XML Parsing

I had a big XML and from which I have to make a layout as below *TOTAL+CB | *CB+FX | CS |*IR | *TOTAL | -------------------------------------------------------------------------------------------------- |CB FX | | | | DMFXNY EMSGFX... (6 Replies)
Discussion started by: manas_ranjan
6 Replies

6. Shell Programming and Scripting

Parsing XML

I am trying to parse an xml file and trying to grab certain values and inserting them into database table. I have the following xml that I am parsing: <dd:service name="locator" link="false"> <dd:activation mode="manual" /> <dd:run mode="direct_persistent" proxified="false" managed="true"... (7 Replies)
Discussion started by: $criptKid617
7 Replies

7. Shell Programming and Scripting

Generating XML from a flatfile

Hi all, I am trying to generate an XML file from a flatfile in ksh/bash (could also use perl at a pinch, but out of my depth there!). I have found several good solutions on this very forum for cases where the header line in the file forms the XML tags, however my flatfile is as follows:... (5 Replies)
Discussion started by: ianmrid
5 Replies

8. Shell Programming and Scripting

Parsing Logfile

Hi, I need to continuously monitor a logfile to get the log information between a process start and end. the logfile look like this abcdddddddddd cjjckkkkkkkkkkkk abc : Process started aaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbbbbbbbbbb abc... (6 Replies)
Discussion started by: Byorg
6 Replies

9. Shell Programming and Scripting

XML: parsing of the Google contacts XML file

I am trying to parse the XML Google contact file using tools like xmllint and I even dived into the XSL Style Sheets using xsltproc but I get nowhere. I can not supply any sample file as it contains private data but you can download your own contacts using this script: #!/bin/sh # imports... (9 Replies)
Discussion started by: ripat
9 Replies

10. Shell Programming and Scripting

XML parsing

i have xml output in below format... <AlertsResponse> <Alert id="11216" name="fgdfg"> <AlertActionLog timestamp="1356521629778" user="admin" detail="Recovery Alert"/> </Alert> <Alert id="11215" name="gdfg <AlertActionLog timestamp="1356430119840" user=""... (12 Replies)
Discussion started by: vivek d r
12 Replies
SED(1)							      General Commands Manual							    SED(1)

NAME
sed - stream editor SYNOPSIS
sed [ -n ] [ -g ] [ -e script ] [ -f sfile ] [ file ... ] DESCRIPTION
Sed copies the named files (standard input default) to the standard output, edited according to a script of commands. The -f option causes the script to be taken from file sfile; these options accumulate. If there is just one -e option and no -f's, the flag -e may be omitted. The -n option suppresses the default output; -g causes all substitutions to be global, as if suffixed g. A script consists of editing commands, one per line, of the following form: [address [, address] ] function [argument ...] In normal operation sed cyclically copies a line of input into a pattern space (unless there is something left after a command), applies in sequence all commands whose addresses select that pattern space, and at the end of the script copies the pattern space to the standard out- put (except under -n) and deletes the pattern space. An address is either a decimal number that counts input lines cumulatively across files, a that addresses the last line of input, or a con- text address, /regular-expression/, in the style of regexp(6), with the added convention that matches a newline embedded in the pattern space. A command line with no addresses selects every pattern space. A command line with one address selects each pattern space that matches the address. A command line with two addresses selects the inclusive range from the first pattern space that matches the first address through the next pattern space that matches the second. (If the second address is a number less than or equal to the line number first selected, only one line is selected.) Thereafter the process is repeated, looking again for the first address. Editing commands can be applied to non-selected pattern spaces by use of the negation function (below). An argument denoted text consists of one or more lines, all but the last of which end with to hide the newline. Backslashes in text are treated like backslashes in the replacement string of an command, and may be used to protect initial blanks and tabs against the stripping that is done on every script line. An argument denoted rfile or wfile must terminate the command line and must be preceded by exactly one blank. Each wfile is created before processing begins. There can be at most 120 distinct wfile arguments. a text Append. Place text on the output before reading the next input line. b label Branch to the : command bearing the label. If label is empty, branch to the end of the script. c text Change. Delete the pattern space. With 0 or 1 address or at the end of a 2-address range, place text on the output. Start the next cycle. d Delete the pattern space. Start the next cycle. D Delete the initial segment of the pattern space through the first newline. Start the next cycle. g Replace the contents of the pattern space by the contents of the hold space. G Append the contents of the hold space to the pattern space. h Replace the contents of the hold space by the contents of the pattern space. H Append the contents of the pattern space to the hold space. i text Insert. Place text on the standard output. n Copy the pattern space to the standard output. Replace the pattern space with the next line of input. N Append the next line of input to the pattern space with an embedded newline. (The current line number changes.) p Print. Copy the pattern space to the standard output. P Copy the initial segment of the pattern space through the first newline to the standard output. q Quit. Branch to the end of the script. Do not start a new cycle. r rfile Read the contents of rfile. Place them on the output before reading the next input line. s/regular-expression/replacement/flags Substitute the replacement string for instances of the regular-expression in the pattern space. Any character may be used instead of For a fuller description see regexp(6). Flags is zero or more of g Global. Substitute for all non-overlapping instances of the regular expression rather than just the first one. p Print the pattern space if a replacement was made. w wfile Write. Append the pattern space to wfile if a replacement was made. t label Test. Branch to the command bearing the label if any substitutions have been made since the most recent reading of an input line or execution of a If label is empty, branch to the end of the script. w wfile Write. Append the pattern space to wfile. x Exchange the contents of the pattern and hold spaces. y/string1/string2/ Transform. Replace all occurrences of characters in string1 with the corresponding character in string2. The lengths of string1 and string2 must be equal. !function Don't. Apply the function (or group, if function is only to lines not selected by the address(es). : label This command does nothing; it bears a label for b and t commands to branch to. = Place the current line number on the standard output as a line. { Execute the following commands through a matching only when the pattern space is selected. An empty command is ignored. EXAMPLES
sed 10q file Print the first 10 lines of the file. sed '/^$/d' Delete empty lines from standard input. sed 's/UNIX/& system/g' Replace every instance of by sed 's/ *$// drop trailing blanks /^$/d drop empty lines s/ */ replace blanks by newlines /g /^$/d' chapter* Print the files chapter1, chapter2, etc. one word to a line. nroff -ms manuscript | sed ' ${ /^$/p if last line of file is empty, print it } //N if current line is empty, append next line /^ $/D' if two lines are empty, delete the first Delete all but one of each group of empty lines from a formatted manuscript. SOURCE
/sys/src/cmd/sed.c SEE ALSO
ed(1), grep(1), awk(1), lex(1), sam(1), regexp(6) L. E. McMahon, `SED -- A Non-interactive Text Editor', Unix Research System Programmer's Manual, Volume 2. BUGS
If input is from a pipe, buffering may consume characters beyond a line on which a command is executed. SED(1)
All times are GMT -4. The time now is 06:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy