I have installed the x2goserver-home package on my linux server. Now I want to open multiple session windows to my server from my x2go client.
I created two session profiles to my server, with the only difference being one of them is named "server1" and the other is named "server2". So, I open a session to server1, and then I try to click on the icon for server2, but nothing happens. Am I missing something?
The only way I was able to open a second session was to run another instance of the x2go client, and then click on the server2 icon.
Is this expected behavior? That I can only open 1 session per x2go client instance?
Dear John,
On Fr 15 Okt 2010 17:23:32 CEST John Williams wrote:
I have installed the x2goserver-home package on my linux server. Now I want to open multiple session windows to my server from my x2go client.
I created two session profiles to my server, with the only difference being one of them is named "server1" and the other is named "server2". So, I open a session to server1, and then I try to click on the icon for server2, but nothing happens. Am I missing something?
The only way I was able to open a second session was to run another instance of the x2go client, and then click on the server2 icon.
Is this expected behavior? That I can only open 1 session per x2go client instance?
Yes, currently this is the expected behaviour. I remember there was
something about multi-session support mentioned in another posting
ages ago on the x2go-dev list, but I am not sure at what position the
feature currently is on Heinz's and Alex's todo list.
Greetings, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, Oct 15, 2010 at 12:25 PM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Yes, currently this is the expected behaviour. I remember there was something about multi-session support mentioned in another posting ages ago on the x2go-dev list, but I am not sure at what position the feature currently is on Heinz's and Alex's todo list.
Okay, thanks for the response.
One other difficulty I have been having with multiple sessions is figuring out which X2Go-client instance corresponds with which X2Go-window instance. This is important when terminating a session, since I do not want to terminate the wrong one!
The problem is that I do not see the session name anywhere, not in the program window, and not in the session window. Am I missing something?
Is there any way for a user to make the session name show up? It could even be pre-pended to the session ID. Anything so I don't have to carefully compare the 10-digit session ID number between the session window and the X2go program window!
I am coming from nomachine NX-client, where you just clicked the close button on the window and it asked whether you wanted to suspend or terminate, which was convenient. Since I am new to x2go, it is possible that I am missing something with x2go that would make it equally convenient.
By the way, I am using the Windows x2go client, v3.01-13
John Williams schreef:
On Fri, Oct 15, 2010 at 12:25 PM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Yes, currently this is the expected behaviour. I remember there was something about multi-session support mentioned in another posting ages ago on the x2go-dev list, but I am not sure at what position the feature currently is on Heinz's and Alex's todo list.
Okay, thanks for the response.
One other difficulty I have been having with multiple sessions is figuring out which X2Go-client instance corresponds with which X2Go-window instance. This is important when terminating a session, since I do not want to terminate the wrong one!
I would say: Close the session before you close X2goclient. Don't terminate a X2go client with status "running".
The problem is that I do not see the session name anywhere, not in the program window, and not in the session window. Am I missing something?
You can see the server and the username when there is a connection. And a SessionID. And a CreationTime.
Is there any way for a user to make the session name show up? It could even be pre-pended to the session ID. Anything so I don't have to carefully compare the 10-digit session ID number between the session window and the X2go program window!
I am coming from nomachine NX-client, where you just clicked the close button on the window and it asked whether you wanted to suspend or terminate, which was convenient. Since I am new to x2go, it is possible that I am missing something with x2go that would make it equally convenient.
X2go just closes the session.
I also don't know a nice way to suspend a session other then using the client-window. Normally I don't suspend sessions. Maybe somebody else knows a way.
When you are using a PGP-card as authentication, the session is suspended when you remove the card.
By the way, I am using the Windows x2go client, v3.01-13
I am talking about the Linux client. No idea if there is much difference, because I have never used the Windows client.
With regards, Paul van der Vlis.
On Tue, Oct 19, 2010 at 6:29 AM, Paul van der Vlis <paul@vandervlis.nl> wrote:
I would say: Close the session before you close X2goclient. Don't terminate a X2go client with status "running".
I may not have been clear in my previous message. Let me define some terms so that we can be sure we understand each other:
x2go-client (X2C): this is the program and window that first gives you a choice of starting an x2go session, and once a session is started, it gives the options of "share folder...", "suspend", or "terminate".
x2go-session (X2S) window: this is the window that displays the remote session running on the x2go server. The only options are the standard window options, like "X", "_", and full-screen.
So, if I close the X2S window by clicking "X", then the session gets suspended. But the only way I see to then terminate the session is to click "cancel" in the X2C window, and then click to start a new session, and then X2C gives me a list of running and suspended sessions, but it only tells me the display number, the status, and the command of each session. That is even less information than when the session is running! So I do not want to terminate it from that list, since I may make a mistake!
You can see the server and the username when there is a connection. And a SessionID. And a CreationTime.
Yes, the X2C window displays Session ID, Server, Username, Display, Creation Time, and Status.
But it does not display the session name! That is the name that you create yourself. You type it in at the top when you create a session profile. I think it is useful to have when keeping track of multiple sessions, since I try to define several different session names to help me keep track.
This is a habit I developed when using the NX client, since it does display the session names in the list of suspended sessions. In fact, with NX client if your server only has 1 suspended session with the session name that you try to start from the client, then the client will automatically resume that session on the server without the user even having to choose from a list of suspended sessions. That is a useful feature.
X2go just closes the session.
There are two ways to close the session: suspending it, in which case the session keeps running, but without displaying a window on the client (and you can later resume it on any other client machine), or terminating it, in which case the session is no longer running, and cannot be resumed.
If you just click on "X" in the X2S window, then x2go suspends the session. I determined that just by trying it to see. If you want to terminate a session, you have to specifically click on the "terminate" button in the X2C window.
I also don't know a nice way to suspend a session other then using the client-window. Normally I don't suspend sessions. Maybe somebody else knows a way.
As I mentioned, suspending a session is easy -- just click on the "X" on the X2S window. It is terminating a session that is more difficult.
I generally have a lot of sessions, both running and suspended, on the server, so the kind of issues I am mentioning come up a lot for me.
I am talking about the Linux client. No idea if there is much difference, because I have never used the Windows client.
I guess there is not much difference, but I thought I would mention it just in case.
John Williams schreef:
On Tue, Oct 19, 2010 at 6:29 AM, Paul van der Vlis <paul@vandervlis.nl> wrote:
I would say: Close the session before you close X2goclient. Don't terminate a X2go client with status "running".
I may not have been clear in my previous message. Let me define some terms so that we can be sure we understand each other:
x2go-client (X2C): this is the program and window that first gives you a choice of starting an x2go session, and once a session is started, it gives the options of "share folder...", "suspend", or "terminate".
x2go-session (X2S) window: this is the window that displays the remote session running on the x2go server. The only options are the standard window options, like "X", "_", and full-screen.
I don't think I understand you wrong.
So, if I close the X2S window by clicking "X", then the session gets suspended.
Hmm, you are right. Clicking the X does suspend the session.
But the only way I see to then terminate the session is to click "cancel" in the X2C window, and then click to start a new session, and then X2C gives me a list of running and suspended sessions, but it only tells me the display number, the status, and the command of each session. That is even less information than when the session is running! So I do not want to terminate it from that list, since I may make a mistake!
What I do normally, is to log-out the user in the session. Then the session terminates.
You can see the server and the username when there is a connection. And a SessionID. And a CreationTime.
Yes, the X2C window displays Session ID, Server, Username, Display, Creation Time, and Status.
But it does not display the session name! That is the name that you create yourself. You type it in at the top when you create a session profile. I think it is useful to have when keeping track of multiple sessions, since I try to define several different session names to help me keep track.
I give the session the same name as the server where I connect to.
This is a habit I developed when using the NX client, since it does display the session names in the list of suspended sessions. In fact, with NX client if your server only has 1 suspended session with the session name that you try to start from the client, then the client will automatically resume that session on the server without the user even having to choose from a list of suspended sessions. That is a useful feature.
X2go just closes the session.
There are two ways to close the session: suspending it, in which case the session keeps running, but without displaying a window on the client (and you can later resume it on any other client machine), or terminating it, in which case the session is no longer running, and cannot be resumed.
If you just click on "X" in the X2S window, then x2go suspends the session. I determined that just by trying it to see. If you want to terminate a session, you have to specifically click on the "terminate" button in the X2C window.
No, you can also do it in the session by logging out the user.
I also don't know a nice way to suspend a session other then using the client-window. Normally I don't suspend sessions. Maybe somebody else knows a way.
As I mentioned, suspending a session is easy -- just click on the "X" on the X2S window. It is terminating a session that is more difficult.
Log out the user.
I generally have a lot of sessions, both running and suspended, on the server, so the kind of issues I am mentioning come up a lot for me.
Do you make many connections to the same server? Why?
I am talking about the Linux client. No idea if there is much difference, because I have never used the Windows client.
I guess there is not much difference, but I thought I would mention it just in case.
I think that too.
With regards, Paul van der Vlis.
On Tue, Oct 19, 2010 at 8:03 AM, Paul van der Vlis <paul@vandervlis.nl> wrote:
What I do normally, is to log-out the user in the session. Then the session terminates.
Thank you for that tip! I did not know that, but I just tried it and it works for me, too!
So, now I know that I can terminate a session by "Log Out..." from within the session. And I can suspend a session by clicking on the "X" of the X2S window.
Now if only the list of suspended and running sessions (the list that pops up when you try to start a session on a server that already has sessions) would include the session name, I would be able to manage all my sessions efficiently.
I give the session the same name as the server where I connect to.
That is less useful for me since I have multiple sessions on the same server. Usually I name the sessions with the server name and then a number or suffix to identify the purpose of the session.
Do you make many connections to the same server? Why?
Yes, at the moment I have 5 sessions on my main server. I have several computers in the house, and generally each computer has at least 1 session running or suspended on the server. Sometimes I have two or more client sessions running on the same client computer, since I sometimes use sessions for a certain task or application. That way I can resume the session from another computer without disturbing the other task(s) that are running on the client computer that was running the session before I switched the session to another computer. Whew, that was a mouthful. But hopefully you get the idea.
John Williams schreef:
On Tue, Oct 19, 2010 at 8:03 AM, Paul van der Vlis <paul@vandervlis.nl> wrote:
What I do normally, is to log-out the user in the session. Then the session terminates.
Thank you for that tip! I did not know that, but I just tried it and it works for me, too!
So, now I know that I can terminate a session by "Log Out..." from within the session. And I can suspend a session by clicking on the "X" of the X2S window.
Now if only the list of suspended and running sessions (the list that pops up when you try to start a session on a server that already has sessions) would include the session name, I would be able to manage all my sessions efficiently.
I agree. But isn't this the same as in Nomachine NX client?
I give the session the same name as the server where I connect to.
That is less useful for me since I have multiple sessions on the same server. Usually I name the sessions with the server name and then a number or suffix to identify the purpose of the session.
Do you make many connections to the same server? Why?
Yes, at the moment I have 5 sessions on my main server. I have several computers in the house, and generally each computer has at least 1 session running or suspended on the server. Sometimes I have two or more client sessions running on the same client computer, since I sometimes use sessions for a certain task or application. That way I can resume the session from another computer without disturbing the other task(s) that are running on the client computer that was running the session before I switched the session to another computer. Whew, that was a mouthful. But hopefully you get the idea.
I understand it a bit.
I agree, it would be nice if it would be easier to give a session a nice name, not some complex ID.
But I think when you have only one suspended session as a user, you don't get any question, the session just starts.
And if you have more then one session as a user, you can easy get problems. E.g. if you start Iceweasel/Firefox it will kill the Iceweasel/Firefox in another session.
With regards, Paul van der Vlis.
On Tue, Oct 19, 2010 at 8:52 AM, Paul van der Vlis <paul@vandervlis.nl> wrote:
I agree. But isn't this the same as in Nomachine NX client?
No, the nomachine NX client will display a list that includes the session names (the names that the user has chosen to type in) when you attempt to start a new session. That is a good feature of the NX client / freenx server.
But I think when you have only one suspended session as a user, you don't get any question, the session just starts.
True, but not very helpful to people like me, who usually have many sessions on the server.
And if you have more then one session as a user, you can easy get problems. E.g. if you start Iceweasel/Firefox it will kill the Iceweasel/Firefox in another session.
That is not a problem. Just use the firefox -no-remote option.
Hi John & Paul,
On Di 19 Okt 2010 17:52:54 CEST Paul van der Vlis wrote:
John Williams schreef: I agree, it would be nice if it would be easier to give a session a nice name, not some complex ID.
I think the profile name in the top frame bar of the X2S window would
suffice, wouldn't it? I will put it on the wishlist for pyhoca-cli.
But I think when you have only one suspended session as a user, you don't get any question, the session just starts.
If the session has really been suspended on closing the X2S window,
then: yes, the only suspended session for this user will be
automatically resumed.
However, if you just click the [x] on the X2S window the session often
stays in running state (AFAIK) and then the x2goclient offers you the
session list with only one session in it. Before resuming a session,
you have to suspend the session from this session list window. Only
then, you can resume your session.
You can also suspend an X2go session from within the session itself.
For GNOME, please install the package x2gognomebindings, for KDE
x2gokdebindings. I have only tested it with GNOME... In case of GNOME,
in the ,,System'' menu you get an extra menu item that says something
like ,,Suspend X2go session''. Use this menu item to suspend your
session.
Greets, mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wed, Oct 20, 2010 at 5:14 AM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi John & Paul,
On Di 19 Okt 2010 17:52:54 CEST Paul van der Vlis wrote:
John Williams schreef: I agree, it would be nice if it would be easier to give a session a nice name, not some complex ID.
I think the profile name in the top frame bar of the X2S window would suffice, wouldn't it? I will put it on the wishlist for pyhoca-cli.
I think that was actually Paul, but I also suspect we are in agreement.
I've been calling the name that the user types in when defining a profile the "session name". That is what it is labeled in the Windows client.
And yes, it would be handy if the session name could be displayed whenever possible. It would be very useful to me if the session names were included in the list of sessions that the client displays when you try to start a new session.
Hi there,
On Mi 20 Okt 2010 16:33:22 CEST John Williams wrote:
On Wed, Oct 20, 2010 at 5:14 AM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi John & Paul,
On Di 19 Okt 2010 17:52:54 CEST Paul van der Vlis wrote:
John Williams schreef: I agree, it would be nice if it would be easier to give a session a nice name, not some complex ID.
I think the profile name in the top frame bar of the X2S window would suffice, wouldn't it? I will put it on the wishlist for pyhoca-cli.
I just looked at nxproxy options... The X2S window title is set by the
X2go server (nxagent option ,,id''). Thus, without changing the X2go
server's communication protocol it is not possible to show the
X2goCLient's session/profile name in the window title.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wed, Oct 20, 2010 at 1:26 PM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi there,
On Mi 20 Okt 2010 16:33:22 CEST John Williams wrote:
On Wed, Oct 20, 2010 at 5:14 AM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi John & Paul,
On Di 19 Okt 2010 17:52:54 CEST Paul van der Vlis wrote:
John Williams schreef: I agree, it would be nice if it would be easier to give a session a nice name, not some complex ID.
I think the profile name in the top frame bar of the X2S window would suffice, wouldn't it? I will put it on the wishlist for pyhoca-cli.
I just looked at nxproxy options... The X2S window title is set by the X2go server (nxagent option ,,id''). Thus, without changing the X2go server's communication protocol it is not possible to show the X2goCLient's session/profile name in the window title.
That is unfortunate. What about the Session ID, can the client set that? If the Session name were prepended to the Session ID (which is shown in the X2S window title), that would be helpful.
Hi John,
On Mi 20 Okt 2010 22:35:09 CEST John Williams wrote:
On Wed, Oct 20, 2010 at 1:26 PM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi there,
On Mi 20 Okt 2010 16:33:22 CEST John Williams wrote:
On Wed, Oct 20, 2010 at 5:14 AM, Mike Gabriel <m.gabriel@das-netzwerkteam.de> wrote:
Hi John & Paul,
On Di 19 Okt 2010 17:52:54 CEST Paul van der Vlis wrote:
John Williams schreef: I agree, it would be nice if it would be easier to give a session a nice name, not some complex ID.
I think the profile name in the top frame bar of the X2S window would suffice, wouldn't it? I will put it on the wishlist for pyhoca-cli.
I just looked at nxproxy options... The X2S window title is set by the X2go server (nxagent option ,,id''). Thus, without changing the X2go server's communication protocol it is not possible to show the X2goCLient's session/profile name in the window title.
That is unfortunate. What about the Session ID, can the client set that? If the Session name were prepended to the Session ID (which is shown in the X2S window title), that would be helpful.
No, the Session ID is generated on the X2go server, as far as I know.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
John Williams -
Mike Gabriel -
Paul van der Vlis