[SOLVED] Bash/Sed : Long time (seconds) between print of last line and script termination

sumncguy · 11-03-2014, 07:05 PM

This snip works but there is a long lag time between the last line printed and the termination of the script. I set x but that didnt show me anything. Im wondering why this is happening.

Code:

grep -E 'tcp.*ssh|tcp.*telnet|udp.*snmp|Host is|scan report' fileone | sed -n "/^Nmap.*)$/,/^161/p" zee |\
sed '
s/\(SNMP.*\|OpenSSH.*$\|protocol.*\)//g;
s/^Nmap.*for //g;
s/Host is //g;
s/(.*latency.*$//g;
s/\(.*cp  \|.*dp \)//g;
s/\((\|)\)//g;
s/ *$//g' | tr '\012' ',' | sed 's/snmp,/snmp\n/g'

grail · 11-03-2014, 11:16 PM

Well I am not sure I follow the process??

You are grepping certain regexes and then asking sed to read both from standard input and the file 'zee'. Is this desired?

As for the delay, one possible reason may be the size of the data being processed. Remember that sed is a stream editor so it processes the entire
stream as it is received. So if the last line which provides data is within the first few of millions of lines, it could take a while to finish.

---------- Post added 04-11-14 at 13:17 ----------

Well I am not sure I follow the process??

You are grepping certain regexes and then asking sed to read both from standard input and the file 'zee'. Is this desired?

As for the delay, one possible reason may be the size of the data being processed. Remember that sed is a stream editor so it processes the entire
stream as it is received. So if the last line which provides data is within the first few of millions of lines, it could take a while to finish.

sumncguy · 11-04-2014, 07:04 AM

Tsch .. embarrassing ... But yes I do see that. Gotta remember to "keep it simple stupid"

thanks for the second eyeball.