Came by to say that, indeed, I'm seeing the exact same behavior in plotly's log on my Yun with the newest image. It gets a few datapoints through to Plotly's server, then I see string of "Connection Refused" errors and nothing gets sent.
Again, if you can downgrade and confirm that 1.0 is working better, please report back. Unfortunately, just saying that "it was working better" doesn't help spotting the bug
Sorry for the delay in my answer, i can now explain exactly what happened.
I have a sketch that upon reception of a certain message over a software serial (connected to a PIC microcontroller) triggers a php script via Process.Run() (is a "php-cli myscript.php " command).
That php script can take long to execute (it waits for a certain action executed by the PIC), and it was an higher time than the watchdog set on the 32u4 (8 seconds).
Reading the forum i discovered that Process.Run waits for the output of the command (while Runasincronously does not) but what is very important is that if the Process object is destroyed, also the started process is destroyed too.
So at first i tried with run.asyncronously ....the sktech was not resetting anymore but as soon as i returned from the function (destroynd the Process object) the linux command was destroyed too.
With this first change i was not getting anymore the connection refused error (because sketch was always running) but my script was not running entirely.
At last, when i discovered Process behaviour i executed my script with "nohup" command at beginning to avoid disruption of the process.
May i suggest to add an option to the Process.Run to destroy or not destroy the process ?
Hope to be helpful for somebody....
Ettore
PS: of course last version, at least for me, seems ok!
Yes, i can do it but i think that as soon as i use Process.begin() my previous command would be destroyed....
since i need to execute lots of commands (can be 2-3 at the same time) i need a way to avoid disruption of the linux process....
I understand but i can not know the max number of process: it is an error detection system so i may have zero errors or 10 concurrent errors (wiith scripts to be executed) so it has been easier to avoid linux SIGTERM the process!