Magic Banana wrote:
>> tee twixt - | dig -f twixt
> That should be 'tee twixt | dig -f -'
In the meantime I had been forced to change 'tee twixt -' to 'tee twixt' in
the process of troubleshooting ...
> ... (or only 'dig -f -' if you do not want to save "twixt")...
My dig scripts had been curtailed by a 'dig -' error caused because the
twixt file was getting chopped off mid-output, ending,
not in lines containing '-x [ipv4]' three times, but in an entry curtailed
before one of the -x fields finished (65.5kB).
I divided my ~30,000 row input file into ten ~3000 row files, and now the
first three of those completed with no errors,
but only about half-way through the subdivided input files, always with twixt
= 65.5 kB. The last of the twixt files ends
thusly:
>>> -x 113.203.238.179 -x 179.238.203.113 -x 203.238.179.113
>>> -x 46.143.247.52 -x 52
It appears to me that the awk script runs first, and in a very short time,
followed one-by-one by the dig and grep scripts.
'tee twixt' apparently fills up the buffer, leading me to skip that step and
go directly to your 'dig -f -' suggestion.
> for the same reason I explained you four times. If 'dig' does not
understand "-" as "standard input", write:
> 'tee twixt | dig -f /dev/stdin'
Right now, the following syntax looks better and processes the entirety of
the subdivided input file:
time tr -sc 0-9\\n ' ' < Input-shuf-01.txt | awk '{ k = 0; for (i = 0; k < 4
&& ++i
