On Thu, Apr 9, 2015 at 8:25 PM, Mihai Moldovan <ionic@ionic.de> wrote:
On 10.04.2015 02:05 AM, Michael DePaulo wrote:
Most beginner Linux sysadmins know that bad things will happen if you delete /etc/passwd. Very few beginner Linux sysadmins know that your desktop environment might not start if you have weird syntax in ~/.*profile or ~/.*rc . A moderately skilled Linux sysadmin who rarely uses a GUI is unlikely to know about this also.
So I think we should document it somewhere on the wiki, perhaps under a troubleshooting section.
On 10.04.2015 02:05 AM, Robert Dinse wrote:
It might be something to add to the troubleshooting section ofthe Wiki.
That sounds very reasonable.
Also, a more helpful error message might still be worth implementing.
Mh, nope. There's no error message, because there was no error, as far as X2Go Client/nx is concerned. A command was successfully started and terminated. Although a "stray" bash process is not what the user *intended* to get, it's what the command ultimately did.
The only way to detect a session almost immediately terminating is to track the time between x2goruncommand start and session termination. If that's too low, say, under a minute, print out an error message. But this will also cause a false positive if the user really *intended* to terminate the session very quickly - for whatever reason. Maybe because it was meant as a quick test to see if X2Go is working at all.
I'd like to avoid such ambiguity.
I was thinking more like 5 seconds. Or perhaps 2 seconds if that turns out to be sufficient empirically.
I can generally change the error message Chris did get by sheer "luck" the second time around, but the point is that this (in this special case unhelpful) error message doesn't even come up reproducibly -- because a successfully created or attached session terminating is in general no error, as explained above.
Mihai
OK, this was the point of confusion. I was thinking for some reason that he got this error message reproducibly.
-Mike