05-12-2005
awk '{ if ($1 ~ /^[0-9]/) { Ln=$0;getline;print Ln" "$0 }}' <filename> will do it
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I need to develop a script to join multiple three lines in a log file into one line for processing with awk and grep. I looked at tr with no success. The first line contains the date time information. The second line contains the error line. The third line is a blank line.
Thanks,
Mike (3 Replies)
Discussion started by: bubba112557
3 Replies
2. UNIX for Dummies Questions & Answers
sir... am having a data file of customer master., containing some important fields as a set one line after another.,
what i want is to have one set of these fields(rows) one after another in line.........then the second set... and so on... till the last set completed.
... (0 Replies)
Discussion started by: KANNI786
0 Replies
3. UNIX for Dummies Questions & Answers
sir... am having a data file of customer master., containing some important fields as a set one line after another.,
what i want is to have one set of these fields(rows) one after another in line.........then the second set... and so on... till the last set completed.
I WANT THE DATA... (0 Replies)
Discussion started by: KANNI786
0 Replies
4. Shell Programming and Scripting
Hi All
I'm struggling a bit here :(
I need a way of joining lines contained in a text file. I've seen numerous SED and AWK examples and none of them seem to be working for me.
The text file has 4 lines:
DELL1427
DOC
30189342
79
Now bear with me on this one as I'm actually... (4 Replies)
Discussion started by: huskie69
4 Replies
5. Shell Programming and Scripting
I’m writing a bash shell script and I want to join lines together where two variables on each line are the same ie.
12345variablestuff43212morevariablestuff
12345variablestuff43212morevariablestuff
34657variablestuff78945morevariablestuff
34657variablestuff78945morevariablestuff... (12 Replies)
Discussion started by: Cultcha
12 Replies
6. Shell Programming and Scripting
I'm looking for a way to join lines in a file; e.,g consider the following
R|This is line 1
R|This is
line 2
R|This is line 3
R|This is line 4
R|This is
line 5
what i want to end up with is
R|This is line 1
R|This is line 2
R|This is line 3
R|This is line 4
R|This is line 5
so... (15 Replies)
Discussion started by: Storms
15 Replies
7. Shell Programming and Scripting
Hi,
I have a file like mentioned below..For each specific id starting with > I want to join the sequence in multiple lines to a single line..Is there a simple way in awk or sed to do this
>ENST00000558922 cdna:KNOWN
TCCAGGATCCAGCCTCCCGATCACCGCGCTAGTCCTCGCCCTGCCTGGGCTTCCCCAGAG... (2 Replies)
Discussion started by: Diya123
2 Replies
8. Shell Programming and Scripting
Hi,
I have a pipe delimeted text file where lines have been split over 2 lines and I need to join them back together. For example the file I have is similar to the following:
aaa|bbb
|ccc
ddd|eee
fff|ggg
|hhh
I ideally need to have it looking like the following
aaa|bbb|ccc
ddd|eee... (5 Replies)
Discussion started by: fuji_s
5 Replies
9. Shell Programming and Scripting
Hi,
I have a file containing many records delimited by pipe (|).
Each record should contain 17 columnns/fields. there are some fields having fields less than 17.So i am extracting those records to a file using the below command
awk 'BEGIN {FS="|"} NF !=17 {print}' feedfile.txt... (8 Replies)
Discussion started by: TomG
8 Replies
10. Shell Programming and Scripting
Hi to everybody.
I have a "2n" lines file. I would like to create a
new file with only "n" lines, each line in the new
file formed by the proper odd line of the old file
joined with the following even line (separated by
a space) of the old file. I'd prefer using sed or
bash.
-example-... (5 Replies)
Discussion started by: felino
5 Replies
LEARN ABOUT DEBIAN
log::agent::channel::handle
Agent::Channel::Handle(3pm) User Contributed Perl Documentation Agent::Channel::Handle(3pm)
NAME
Log::Agent::Channel::Handle - I/O handle logging channel for Log::Agent
SYNOPSIS
require Log::Agent::Channel::Handle;
my $driver = Log::Agent::Channel::Handle->make(
-prefix => "prefix",
-stampfmt => "own",
-showpid => 1,
-handle => *FILE,
);
DESCRIPTION
The handle channel performs logging to an already opened I/O handle, along with the necessary prefixing and stamping of the messages.
The creation routine make() takes the following arguments:
"-handle" => handle
Specifies the I/O handle to use. It can be given as a GLOB reference, such as "*FILE", or as an "IO::Handle" object.
NOTE: Auto-flushing is not enabled on the handle. Even when the channel is closed, the handle is left as-is: we simply stop sending
log messages to it.
"-no_newline" => flag
When set to true, never append any "
" (on Unix) or "
" (on Windows) to log messages.
Internally, Log::Agent relies on the channel to delimit logged lines appropriately, so this flag is not used. However, it might be
useful for "Log::Agent::Logger" users.
Default is false, meaning newline markers are systematically appended.
"-no_prefixing" => flag
When set to true, disable the prefixing logic entirely, i.e. the following options are ignored completely: "-prefix", "-showpid",
"-no_ucfirst", "-stampfmt".
Default is false.
"-no_ucfirst" => flag
When set to true, don't upper-case the first letter of the log message entry when there's no prefix inserted before the logged line.
When there is a prefix, a ":" character follows, and therefore the leading letter of the message should not be upper-cased anyway.
Default is false, meaning uppercasing is performed.
"-prefix" => prefix
The application prefix string to prepend to messages.
"-showpid" => flag
If set to true, the PID of the process will be appended within square brackets after the prefix, to all messages.
Default is false.
"-stampfmt" => (name | CODE)
Specifies the time stamp format to use. By default, my "own" format is used. See Log::Agent::Stamping for a description of the
available format names.
You may also specify a CODE ref: that routine will be called every time we need to compute a time stamp. It should not expect any
parameter, and should return a string.
CAVEAT
Beware of chdir(). If your program uses chdir(), you should always specify logfiles by using absolute paths, otherwise you run the risk of
having your relative paths become invalid: there is no anchoring done at the time you specify them. This is especially true when
configured for rotation, since the logfiles are recreated as needed and you might end up with many logfiles scattered throughout all the
directories you chdir()ed to.
AUTHOR
Raphael Manfredi <Raphael_Manfredi@pobox.com>
SEE ALSO
Log::Agent::Logger(3), Log::Agent::Channel(3).
perl v5.10.0 2002-03-09 Agent::Channel::Handle(3pm)