[Ovmsdev] Console output batched up while command is run #32
casner at acm.org
Fri Apr 13 05:00:22 HKT 2018
Would you like me to modify the Mongoose code to add an option flag so
that mg_send() will send immediately if it would not block (the way it
behaved with my modifications before you updated to a newer version)?
On Tue, 10 Apr 2018, Stephen Casner wrote:
> This phenomenon is a consequence of the Mongoose behavior of buffering
> all the data rather than sending immediately. We talked about some
> approaches for an option to control that behavior, but I did not
> implement any at the time since we were running with an unmodified
> Mongoose at that point and we were not hitting memory crashes after
> the adjustments we had made with tasks and stacks.
> Subsequently we did decide to maintain some modifications to Mongoose,
> so perhaps now I should implement an option for immediate sending.
> -- Steve
> On Tue, 10 Apr 2018, Mark Webb-Johnson wrote:
> > Another one for Steve:
> > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/32 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/32>
> > When running commands in ssh console (maybe others), the output is batched up and only output when the command has finished running.
> > An example is:
> > test sd
> > But also:
> > ota flash http
> > It would be better if it could be output as the command is run.
> > The issue is that we get no output when the command is run, then 30 seconds later (when command finishes) everything comes in one big batch output. The progress messages issued while the command runs are batched up.
> > I don’t know how easy this is (I fear it is fundamental), but please have a look.
> > Thanks, Mark.
More information about the OvmsDev