Greetings all;

As you know, I do a lot of gcode writing on my machines that occasionally 
needs to restart linuxcnc, but if I've left it running from its own 
console, and I'm here in the house in the middle of the night, and I 
want to see what my cde looks like in the backplot, that means LCNC has 
to send itself a killall.  That usually works but because it doesn't 
wait long enough, the restart fails, so you have to up=arrow and run it 
again to actually start the new session. Thats expected.

But for the last day, the window here, or there, has been stuck in a loop 
reporting an invalid status buffer at about 100 lines a second. I can 
kill that login and start a new one, looking it over with htop without 
noting anything out of place, but the machine isn't responding quite as 
snappy as before unless I reboot it. And I just updated linuxcnc from 
master after this reboot, the version it was running was maybe 1.5 days 
old. With two logins, I'm going to repeat this "start a new session of 
linuxcnc and see if it repeats this strange behaviour, and hopfully 
capture the error message.
Started it from one ssh login, then went to the other and started another 
session. Fails of course. Repeat from 2nd login and this time it worked 
w/o flooding the first login with the error message about an invalid 
status buffer.

But now, with the newer linuxcnc I just updated to, no error is logged to 
the screen being shut down, AND the restart on the alternate login is 
successful w/o the 2nd start needing to be issued. And I have bounced 
back and forth 4 times now, successfully each time.

Is there that big a difference between its own konsole and an ssh -Y 
login? Or has this loooonnnnggstanding bug (what, 10 years now?,) 
actually been fixed? New version is LINUXCNC - 2.8.0-pre1-4575-g59380be

In which case a hearty thank you is now sent!

Here I was going to submit a bug report, but now I can't, thank you very 
much guy's.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>



_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to