Very Computer

Hi,

I'm trying to read in from an SQL*Loader log file and read the four
numbers provided as summary load counts into a shell script array
using:

grep "^Total logical records" gnis_native.log | sed "s/.*: *//g" | tr
'\n' ' '

Except tr gives me a null output and whilst sed gives me:
xxx
xxx
xxx

Where xxx is a number. Any ideas?

The gnis_native.log is available:
http://examples.oreilly.com/orsqlloader/

See the logs below.

grep "^Total logical records" gnis_native.log
+ grep ^Total logical records gnis_native.log
Total logical records skipped:          0
Total logical records read:            58
Total logical records rejected:        51
Total logical records discarded:        0

grep "^Total logical records" gnis_native.log | sed "s/.*: *//g"
+ sed s/.*: *//g
+ grep Total logical records gnis_native.log
0
58
51
0

grep "^Total logical records" gnis_native.log | sed "s/.*: *//g" | tr
'\n' ' '
+ grep Total logical records gnis_native.log
+ tr \n
+ sed s/.*: *//g

I'm guessing that the line is still in a buffer somewhere,
since tr '\n' ' ' also changes the last \n to a space.

Try:

(grep ... | tr '\n' ' '; echo "")

The echo will add a newline, allowing the line to print.

Bill Seivert

Maybe you've got control-Ms or some other control characters in the file.

Quote:> The gnis_native.log is available:
> http://examples.oreilly.com/orsqlloader/

I didn't see it there.

Quote:> See the logs below.

> grep "^Total logical records" gnis_native.log
> + grep ^Total logical records gnis_native.log
> Total logical records skipped:          0
> Total logical records read:            58
> Total logical records rejected:        51
> Total logical records discarded:        0

> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g"
> + sed s/.*: *//g
> + grep Total logical records gnis_native.log
> 0
> 58
> 51
> 0

Why does the "sed" appear before the "grep" in the "set -x" trace?

Quote:> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g" | tr
> '\n' ' '
> + grep Total logical records gnis_native.log
> + tr \n
> + sed s/.*: *//g

That appears to be doing a grep then a tr then a sed. Try this:

awk '/^Total logical records/{printf "%s ",$NF}END{print ""}'
gnis_native.log

and see if it fares any better.

        Ed.

Ed - that is how pipelines are displayed with shell tracing turned on...

Quote:>> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g" | tr
>> '\n' ' '
>> + grep Total logical records gnis_native.log
>> + tr \n
>> + sed s/.*: *//g

> That appears to be doing a grep then a tr then a sed. Try this:

> awk '/^Total logical records/{printf "%s ",$NF}END{print ""}'
> gnis_native.log

> and see if it fares any better.

Kevin

Not in any of the environments I use, e.g. bash under cygwin:

PS1> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g"
+ grep '^Total logical records' gnis_native.log
+ sed 's/.*: *//g'

Good to know it can become twisted in some other environments though -
could save me some needless debugging in future!

        Ed.

I guess I should amend that to say "could be" instead of "are".

Quote:> Not in any of the environments I use, e.g. bash under cygwin:

> PS1> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g"
> + grep '^Total logical records' gnis_native.log
> + sed 's/.*: *//g'

> Good to know it can become twisted in some other environments though -
> could save me some needless debugging in future!

Here it is from HP-UX 11.11 running ksh:

-> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g"
+ sed s/.*: *//g
+ grep ^Total logical records gnis_native.log

Here it is on RHEL 3 running pdksh (in the "right" order):

-> grep "^Total logical records" gnis_native.log | sed "s/.*: *//g"
+ grep ^Total logical records gnis_native.log
+ sed s/.*: *//g

Since I do most of my work on HP-UX (and have for a long time), I am used to
the "backwards" listing... :)

Kevin