Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Extracting a block of text from a large file using variables? Post 302891074 by RavinderSingh13 on Monday 3rd of March 2014 04:37:14 PM
Old 03-03-2014
Hello Klor,

Following could help you.

EDIT: This should help in all in all data input file.

Code:
awk '/ORBITAL ENERGIES/ {getline;getline;getline;{a=$2" "$3" "$4};getline;{b=$2" "$3" "$4};getline;{c=$2" "$3" "$4};getline} END{print a ORS b ORS c}' check_parameters

Output will be as follows.

Code:
Data2 Data3 Data4
Data2.1 Data3.1 Data4.1
Data2.2 Data3.2 Data4.2


NOTE: Following code will work only for given input in thread.

Code:
awk 'NR==4 || NR==5 {print $2" "$3" "$4}' check_parameters

Output will be as follows.

Code:
Data2 Data3 Data4
Data2.1 Data3.1 Data4.1


NOTE: Where check_parameters is the Input file name.

Thanks,
R. Singh

Last edited by RavinderSingh13; 03-03-2014 at 05:48 PM.. Reason: Adding complete solution
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Parsing file and extracting the useful data block

Greetings All!! I have a very peculiar problem where I have to parse a big text file and extract useful data out of it with starting and ending block pattern matching. e.g. I have a input file like this: sample data block1 sample data start useful data end sample data block2 sample... (5 Replies)
Discussion started by: arminder
5 Replies

2. UNIX for Dummies Questions & Answers

extracting text and reusing the text to rename file

Hi, I have some ps files where I want to ectract/copy a certain number from and use that number to rename the ps file. eg: 'file.ps' contains following text: 14 (09 01 932688 0)t the text can be variable, the only fixed element is the '14 ('. The problem is that the fixed element can appear... (7 Replies)
Discussion started by: JohnDS
7 Replies

3. Shell Programming and Scripting

Performance issue in UNIX while generating .dat file from large text file

Hello Gurus, We are facing some performance issue in UNIX. If someone had faced such kind of issue in past please provide your suggestions on this . Problem Definition: /Few of load processes of our Finance Application are facing issue in UNIX when they uses a shell script having below... (19 Replies)
Discussion started by: KRAMA
19 Replies

4. Shell Programming and Scripting

Help with splitting a large text file into smaller ones

Hi Everyone, I am using a centos 5.2 server as an sflow log collector on my network. Currently I am using inmons free sflowtool to collect the packets sent by my switches. I have a bash script running on an infinate loop to stop and start the log collection at set intervals - currently one... (2 Replies)
Discussion started by: lord_butler
2 Replies

5. Shell Programming and Scripting

Extracting a portion of data from a very large tab delimited text file

Hi All I wanted to know how to effectively delete some columns in a large tab delimited file. I have a file that contains 5 columns and almost 100,000 rows 3456 f g t t 3456 g h 456 f h 4567 f g h z 345 f g 567 h j k lThis is a very large data file and tab delimited. I need... (2 Replies)
Discussion started by: Lucky Ali
2 Replies

6. Shell Programming and Scripting

splitting a large text file into paragraphs

Hello all, newbie here. I've searched the forum and found many "how to split a text file" topics but none that are what I'm looking for. I have a large text file (~15 MB) in size. It contains a variable number of "paragraphs" (for lack of a better word) that are each of variable length. A... (3 Replies)
Discussion started by: lupin..the..3rd
3 Replies

7. Shell Programming and Scripting

extracting block of lines from a file

consider the input file which i am dealing with looks like this.. #cat 11.sql create table abc ( . . . ) engine=Innodb ; . . etc . . . create table UsM ( blah blah blah ) engine=Innodb ; (5 Replies)
Discussion started by: vivek d r
5 Replies

8. Shell Programming and Scripting

help extracting text from file

Hello I have a large file with lines beginning with 552, 553, 554, below is a small sample, I need to extract the data you can see below highlighted in bold from this file on the same location on every line and output it to a new file. Thank you in advance for any help 55201KL... (2 Replies)
Discussion started by: firefox2k2
2 Replies

9. UNIX for Dummies Questions & Answers

Extracting lines from a text file based on another text file with line numbers

Hi, I am trying to extract lines from a text file given a text file containing line numbers to be extracted from the first file. How do I go about doing this? Thanks! (1 Reply)
Discussion started by: evelibertine
1 Replies

10. Shell Programming and Scripting

Awk: passing shell variables through and extracting text

Hello, new to the forums and to awk. Glad to be here. :o I want to pass two shell (#!/bin/sh) variables through to awk and use them. They will determine where to start and stop text extraction. The code with the variables hard-coded in awk works fine; the same code, but with the shell... (7 Replies)
Discussion started by: bedtime
7 Replies
LP(4)							   BSD Kernel Interfaces Manual 						     LP(4)

NAME
lp -- printer port Internet Protocol driver SYNOPSIS
ifconfig plip0 myaddress hisaddress [-link0] device ppbus device plip device ppc DESCRIPTION
The lp driver allows a PC parallel printer port to be used as a point-to-point network interface between two similarly configured systems. Data is transferred 4 bits at a time, using the printer status lines for input: hence there is no requirement for special bidirectional hard- ware and any standard AT-compatible printer port with working interrupts may be used. During the boot process, for each plip device which is probed and has an interrupt assigned, a corresponding network device is created. Configuring an lp device with ifconfig(8) causes the corresponding parallel port bus to be reserved for PLIP until the network interface is configured 'down'. The communication protocol is selected by the link0 flag: -link0 (default) Use FreeBSD mode (LPIP). This is the simpler of the two modes and therefore slightly more efficient. link0 Use Crynwr/Linux compatible mode (CLPIP). This mode has a simulated Ethernet packet header, and is easier to interface to other types of equipment. The interface MTU defaults to 1500, but may be set to any value. Both ends of the link must be configured with the same MTU. Cable Connections The cable connecting the two parallel ports should be wired as follows: Pin Pin Description 2 15 Data0 -> ERROR* 3 13 Data1 -> SLCT 4 12 Data2 -> PE 5 10 Data3 -> ACK* 6 11 Data4 -> BUSY 15 2 ERROR* -> Data0 13 3 SLCT -> Data1 12 4 PE -> Data2 10 5 ACK* -> Data3 11 6 BUSY -> Data4 18-25 18-25 Ground Cables with this wiring are widely available as 'Laplink' cables, and are often coloured yellow. The connections are symmetric, and provide 5 lines in each direction (four data plus one handshake). The two modes use the same wiring, but make a different choice of which line to use as handshake. FreeBSD LPIP mode The signal lines are used as follows: Data0 (Pin 2) Data out, bit 0. Data1 (Pin 3) Data out, bit 1. Data2 (Pin 4) Data out, bit 2. Data3 (Pin 5) Handshake out. Data4 (Pin 6) Data out, bit 3. ERROR* (pin 15) Data in, bit 0. SLCT (pin 13) Data in, bit 1. PE (pin 12) Data in, bit 2. BUSY (pin 11) Data in, bit 3. ACK* (pin 10) Handshake in. When idle, all data lines are at zero. Each byte is signalled in four steps: sender writes the 4 most significant bits and raises the hand- shake line; receiver reads the 4 bits and raises its handshake to acknowledge; sender places the 4 least significant bits on the data lines and lowers the handshake; receiver reads the data and lowers its handshake. The packet format has a two-byte header, comprising the fixed values 0x08, 0x00, immediately followed by the IP header and data. The start of a packet is indicated by simply signalling the first byte of the header. The end of the packet is indicated by inverting the data lines (i.e., writing the ones-complement of the previous nibble to be transmitted) without changing the state of the handshake. Note that the end-of-packet marker assumes that the handshake signal and the data-out bits can be written in a single instruction - otherwise certain byte values in the packet data would falsely be interpreted as end-of-packet. This is not a problem for the PC printer port, but requires care when implementing this protocol on other equipment. Crynwr/Linux CLPIP mode The signal lines are used as follows: Data0 (Pin 2) Data out, bit 0. Data1 (Pin 3) Data out, bit 1. Data2 (Pin 4) Data out, bit 2. Data3 (Pin 5) Data out, bit 3. Data4 (Pin 6) Handshake out. ERROR* (pin 15) Data in, bit 0. SLCT (pin 13) Data in, bit 1. PE (pin 12) Data in, bit 2. ACK* (pin 10) Data in, bit 3. BUSY (pin 11) Handshake in. When idle, all data lines are at zero. Each byte is signalled in four steps: sender writes the 4 least significant bits and raises the hand- shake line; receiver reads the 4 bits and raises its handshake to acknowledge; sender places the 4 most significant bits on the data lines and lowers the handshake; receiver reads the data and lowers its handshake. [Note that this is the opposite nibble order to LPIP mode]. Packet format is: Length (least significant byte) Length (most significant byte) 12 bytes of supposed MAC addresses (ignored by FreeBSD). Fixed byte 0x08 Fixed byte 0x00 <IP datagram> Checksum byte. The length includes the 14 header bytes, but not the length bytes themselves nor the checksum byte. The checksum is a simple arithmetic sum of all the bytes (again, including the header but not checksum or length bytes). FreeBSD calculates outgoing checksums, but does not validate incoming ones. The start of packet has to be signalled specially, since the line chosen for handshake-in cannot be used to generate an interrupt. The sender writes the value 0x08 to the data lines, and waits for the receiver to respond by writing 0x01 to its data lines. The sender then starts signalling the first byte of the packet (the length byte). End of packet is deduced from the packet length and is not signalled specially (although the data lines are restored to the zero, idle state to avoid spuriously indicating the start of the next packet). SEE ALSO
ppbus(4), ppc(4), ifconfig(8) BUGS
Busy-waiting loops are used while handshaking bytes, (and worse still when waiting for the receiving system to respond to an interrupt for the start of a packet). Hence a fast system talking to a slow one will consume excessive amounts of CPU. This is unavoidable in the case of CLPIP mode due to the choice of handshake lines; it could theoretically be improved in the case of LPIP mode. Polling timeouts are controlled by counting loop iterations rather than timers, and so are dependent on CPU speed. This is somewhat sta- bilised by the need to perform (slow) ISA bus cycles to actually read the port. BSD
March 4, 1996 BSD
All times are GMT -4. The time now is 05:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy