Hi Alex,
On Mi 22 Aug 2018 09:01:15 CEST, Oleksandr Shneyder wrote:
Hi Mike,
this feature is activated by broker. If broker is not supporting it,
there are no changes in X2Go Client behavior. I never putting in master
branch commits that supposed to break compatibility with previous
Hi Mike,
My customers have different brokers. Some of them giving back sessions,
depending on broker login, other on x2go server login. One of the examples:
I'm logged on the broker as "Alex", you logged on the broker as "Mike".
Both of us logged on the one of the servers in server pool "Lab-1"
Hi Alex,
On Mi 28 Nov 2018 17:03:52 CET, Oleksandr Shneyder wrote:
Hi Mike,
this parameter is needed for the case if brokeruser and x2gouser are not
same. Until this commit X2Go client only sent broker login to the
broker, and not login name on x2go server.
So if you are connecting to broker
Hi Mike,
unfortunately it's not always possible to get the session state from
X2Go server. One simple example - direct RDP session. Another use case,
sometimes (for example because of security reasons), you can't have
access from X2Go Broker to X2Go Server.
Anyway if you are running the network
Control: close -1
On Do 13 Sep 2018 15:19:19 CEST, Mike Gabriel wrote:
Hi Walid,
On Mo 13 Aug 2018 12:34:00 CEST, Walid MOGHRABI wrote:
package: x2gobroker-agent
version: 0.0.4.0-0~1038~ubuntu16.04.1
priority: bug
I don't have a "0" value anymore since latest fixes so the
loadchecker
Processing control commands:
> close -1
Bug #1313 [x2gobroker-agent] there is still a problem in getting a correct
value for loadavgXX with loadchecker
Marked Bug as done
--
1313: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1313
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with
