Hi,
I've noticed weird behaviour of my home automation controller module (written in Perl) and DCERouter.
- if I start perl script from command line it's output goes fluently on console. If I let Pluto run it under screen, then output is jerky - freezes for few seconds and then advances, etc.... Is this only visual impression or does screen somehow affect how script is running ?
- spotted situation that my module sends events and commands on TCP port to Router, but DCERouter receives nothing - obviously TCP port closed somehow or something else happened. How to prevent or detect and heal this deadlock in general ? Where to check what happened in this particular situation ?
Thanks in advance,
regards,
Rob.
Screen has nothing to do with the output of your script being jerky, i think that when runned by pluto your script behaves differently than when you run it from the console.
The tcp problem i think is also related to your script since if the tcp port was closed the pluto modules would stop working also.
You can type this into a core's console to see if the port is opened:
nc -z localhost 3450 || echo "Port 3450 is closed"