I will try it with the tee. I couldn't get this to work without the sed command, IIRC.
-SR On Friday, November 18, 2016 at 12:00:49 PM UTC-8, mwall wrote: > > On Friday, November 18, 2016 at 2:37:28 PM UTC-5, Sam Roza wrote: >> >> I use interceptor with the following script: >> >> ~~~ >> ngrep -l -q -d eth0 '0004a369e0d6' | sed -u '/mac=/!d' | xargs -n 1 curl >> http://localhost:9999 -s -d >> ~~~ >> >> I can tee it into a file if you think we're losing data. >> > > when debug=1, the interceptor will report any data it receives via POST or > GET > > so the question is whether the ngrep-sed-curl process is filtering out > data from the gateway > > the sed command > > sed -u '/mac=/!d' > > skips any line that does not contain mac=, so if somehow the lines from > the t/h and wind sensor were scrambled/shifted, that command might remove > them. > > you could temporarily try a tee before the sed: > > ngrep -l -q -d eth0 '0004a369e0d6' | tee /var/tmp/dump.txt | sed -u > '/mac=/!d' | xargs -n 1 curl http://localhost:9999 -s -d > > if you see another lapse in data, check the tee output file for strings > that contain x=y&a=b data but no mac= > > or you could simply eliminate the sed altogether, but i'm not sure how > curl would handle that, and although i have made the interceptor more > robust to funky inputs that it used to be, it is still probably not robust > enough. > > m > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
