Arrgh!!! Nevermind the aforesaid, I've just figured things out -- turns out I was wrong when I wrote that the lines 11 and 12 don't contain "begin" or "end". Both lines contain the word "sender".
The carriage returns were a total red herring. I was wrong when I thought that removing them had fixed things. It turns out that when I tested grep after removing them I had only grepped "begin" and not "begin|end".
So it's probably not a good idea to grep for "end" in this case without throwing away the email headers first. In my initial --only partially successful-- approach this also was unnecessary, because tail lends itself really well to clipping off the upper parts of the file without even looking at them (and uudecode ignores anything boyond the first uuencoded file, so the rest can be left as it).
which is entirely understandable, because the command line
Code:
sed -n "11,12p" /tmp/tmp.mail | uudecode
that's generated and passed to sh is bogus, and of course line 11 has no "begin" in it.
I still don't fully understand the nested sed stuff though. I'll try some more and/or come back with more questions. Also, if someone has a hint to get my initial approach with awk and tail to work, that would be really cool.
I want to run tail -f to continuously monitor a log file, outputing a specific field to a second log file. I can get the first portion to work with the following command:
tail -f log | awk '{if ($1 == "Rough") print $5}'
also:
awk '{if ($1 == "Rough") print $5}' <(tail -f log)
The... (2 Replies)
Hi
I have a file with lots of line feeds and form feeds (page break). Need to replace last occurrence of form feed (created by - echo "\f" ) in the file with line feed.
Please advise how can i achieve this.
TIA
Prvn (5 Replies)
Hello,
I am using a tail command to fetch the line before last in a log file.
the two last lines are as followed:
11-01-16 11:55:45.174 | CClientObject::InitTraceLevelInCache Starting
CClientObject::InitTraceLevelInCache End
I am doing a awk statement to gather only the numeric... (1 Reply)
I need some advice, I have live feed containing xml messages which means there is new messages every minute. I need a script that will run every 2 hours using the current time minus 2 hours ( which I able to do) However I have problem with the date formatting i.e.
One date is... (3 Replies)
Hello all,
I have data like
"1"|"My_name"|"My_Email"|"My_Last"|My_other"
"2"|"My_name"|"My_Email"|"My_Last"|My_other"
"3"|"My_name"|"My_Email"|"
"|My_other"
"1"|"My_name"|"My_Email"|"My_Last"|My_other"
Need output like
"1"|"My_name"|"My_Email"|"My_Last"|My_other"... (10 Replies)
Hi Forum.
I have the following script that splits a large fixed-width file into smaller multiple fixed-width files based on input segment type.
The main command in the script is:
awk -v search_col_pos=$search_col_pos -v search_str_len=$search_str_len -v segment_type="$segment_type"... (8 Replies)
Hello,
Can someone please share a Simple AWK command to append Carriage Return & Line Feed to the end of the file, If the Carriage Return & Line Feed does not exist !
Thanks (16 Replies)
Hello,
I would like to write script to tail a file for different environment
But the number of lines are keep changing
How can I write a script
For example:
env could : A, B or C
and log files could be a.log, b.log and c.log
with the number of lines can change
say sometimes it 100 last... (9 Replies)
Discussion started by: encrypt_decrypt
9 Replies
LEARN ABOUT FREEBSD
b64decode
UUENCODE(1) BSD General Commands Manual UUENCODE(1)NAME
uuencode, uudecode, b64encode, b64decode -- encode/decode a binary file
SYNOPSIS
uuencode [-m] [-o output_file] [file] name
uudecode [-cimprs] [file ...]
uudecode [-i] -o output_file
b64encode [-o output_file] [file] name
b64decode [-cimprs] [file ...]
b64decode [-i] -o output_file [file]
DESCRIPTION
The uuencode and uudecode utilities are used to transmit binary files over transmission mediums that do not support other than simple ASCII
data. The b64encode utility is synonymous with uuencode with the -m flag specified. The b64decode utility is synonymous with uudecode with
the -m flag specified.
The uuencode utility reads file (or by default the standard input) and writes an encoded version to the standard output, or output_file if
one has been specified. The encoding uses only printing ASCII characters and includes the mode of the file and the operand name for use by
uudecode.
The uudecode utility transforms uuencoded files (or by default, the standard input) into the original form. The resulting file is named
either name or (depending on options passed to uudecode) output_file and will have the mode of the original file except that setuid and exe-
cute bits are not retained. The uudecode utility ignores any leading and trailing lines.
The following options are available for uuencode:
-m Use the Base64 method of encoding, rather than the traditional uuencode algorithm.
-o output_file
Output to output_file instead of standard output.
The following options are available for uudecode:
-c Decode more than one uuencoded file from file if possible.
-i Do not overwrite files.
-m When used with the -r flag, decode Base64 input instead of traditional uuencode input. Without -r it has no effect.
-o output_file
Output to output_file instead of any pathname contained in the input data.
-p Decode file and write output to standard output.
-r Decode raw (or broken) input, which is missing the initial and possibly the final framing lines. The input is assumed to be in the
traditional uuencode encoding, but if the -m flag is used, or if the utility is invoked as b64decode, then the input is assumed to be
in Base64 format.
-s Do not strip output pathname to base filename. By default uudecode deletes any prefix ending with the last slash '/' for security
reasons.
EXAMPLES
The following example packages up a source tree, compresses it, uuencodes it and mails it to a user on another system. When uudecode is run
on the target system, the file ``src_tree.tar.Z'' will be created which may then be uncompressed and extracted into the original tree.
tar cf - src_tree | compress |
uuencode src_tree.tar.Z | mail user@example.com
The following example unpacks all uuencoded files from your mailbox into your current working directory.
uudecode -c < $MAIL
The following example extracts a compressed tar archive from your mailbox
uudecode -o /dev/stdout < $MAIL | zcat | tar xfv -
SEE ALSO basename(1), compress(1), mail(1), uucp(1) (ports/net/freebsd-uucp), uuencode(5)HISTORY
The uudecode and uuencode utilities appeared in 4.0BSD.
BUGS
Files encoded using the traditional algorithm are expanded by 35% (3 bytes become 4 plus control information).
BSD January 27, 2002 BSD
04-02-2008
Nevermind the aforesaid, I've just figured things out -- turns out I was wrong when I wrote that the lines 11 and 12 don't contain "begin" or "end". Both lines contain the word "sender". 
