Playing around with tail -f, it turned out the unwanted node-red behavior was because I forgot to call fflush().
This didn't matter for the usage it was originally written for. After a quick recompile of the client after adding fflush() I can make very good use of this as a rapid prototype as it is by using the BBG as a middleman, but its probably better I modify the original BBW IOT application to use libmosquito to send message to the broker as my monitoring client exposes all the state variables, many of which are of no use to a client and were only included for test/debug purposes in the client. But my first "real use" of node-red has to be scored a success and it delivered a lot of functionality for minimal effort. Down the road I'll decide if its easier to mod the IOT app to use libmosquito or swap in a new SD card (physical access issues with the BBW). Thanks again for all the help! On Friday, April 29, 2016 at 5:49:18 PM UTC-5, Wally Bkg wrote: > > If I'm the only one with this issue don't worry about it, please move on > to more important things. > > I did test my idea using node-red on the BBG. The mqtt stuff worked > nicely with the BBW as the broker, but my read of how the exec node worked > from the info pane description was wishful thinking. I was wanting one > message for each output line on stdout from the application launched by the > exec node as it runs (its a status monitoring application that prints one > line for each IOT system variable status change, its a client that talks to > a server running on the BBW). What I got was one output message with all > the stdout when I killed the program (deamon) as if I'd piped it to a file > and then cat the file. > > I may play around with piping the output to a file and using the tail node > to generate the messages, but it was just a neat idea that could have been > a "real use" of node-red for me. I probably should have tried this before > trying to upgrade the node-red on the BBW system which ultimately was a > distraction. But at least now I know if I need node-red on the BBW I'll > need to start with a fresh image. > > Thanks again! > > > On Friday, April 29, 2016 at 4:49:00 PM UTC-5, RobertCNelson wrote: >> >> >> >> On Fri, Apr 29, 2016 at 4:41 PM, Wally Bkg <[email protected]> wrote: >> >>> Thanks for the suggestion but it still didn't work: >>> >>> Setting up bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) ... >>> bb-node-red-installer:npm: [2.15.0] >>> bb-node-red-installer:node: [v0.12.13] >>> bb-node-red-installer:Installing: systemd-0.2.6 (for node-red) >>> npm WARN engine [email protected]: wanted: {"node":">=0.6.11 <0.11.0"} >>> (current: {"node":"0.12.13","npm":"2.15.0"}) >>> [email protected] /usr/local/lib/node_modules/systemd >>> bb-node-red-installer:Installing: node-red-0.13.4 (for node-red) >>> >>> > [email protected] install >>> /usr/local/lib/node_modules/node-red/node_modules/bcrypt >>> > node-gyp rebuild >>> >>> >>> Killed >>> dpkg: error processing package bb-node-red-installer (--configure): >>> subprocess installed post-installation script returned error exit >>> status 137 >>> Errors were encountered while processing: >>> bb-node-red-installer >>> E: Sub-process /usr/bin/dpkg returned an error code (1) >>> >> >> I'll double check this on sunday, at work my flash drive only goes back >> too 2016-03-20, but i have all the snapshots on a nas at home.. >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ae7a2248-e9d2-44ae-8cb0-031ec4ee6bd9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
