Hi!
I wanted to run the x2go client from the command line to display the "username" and "password" fields only, like it happens when using pyHoca-GUI. The problem is that whenever my users hit the "CANCEL" button they always see the list of available sessions at the right of the window, which I wanted to avoid.
I've tried a command line such as:
x2goclient.exe --no-session-edit --disable-pulse --session=MYSESSION --close-disconnect --hide-foldersharing --no-autoresume --no-menu
I don't want to use the pyHoca-GUI because it's too slow to start (at least in our environment)
Thanks,
alaxa
Am 25.06.2018 um 11:16 schrieb alaxa@libero.it:
Hi!
I wanted to run the x2go client from the command line to display the "username" and "password" fields only, like it happens when using pyHoca-GUI. The problem is that whenever my users hit the "CANCEL" button they always see the list of available sessions at the right of the window, which I wanted to avoid.
The question is: Why do you offer more than one session type to your users, when they are supposed to use only one?
The way to solve this will depend on your answer.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient. At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings. Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux"
then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface.
Thanks, alaxa
Il 25 giugno 2018 alle 12.41 Stefan Baur <X2Go-ML-1@baur-itcs.de> ha scritto: Am 25.06.2018 um 11:16 schrieb alaxa@libero.it: > >Hi! I wanted to run the x2go client from the command line to display the "username" and "password" fields only, like it happens when using pyHoca-GUI. The problem is that whenever my users hit the "CANCEL" button they always see the list of available sessions at the right of the window, which I wanted to avoid. >The question is: Why do you offer more than one session type to your users, when they are supposed to use only one? The way to solve this will depend on your answer. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Hi Alaxa,
Am 25.06.2018 um 20:17 schrieb alaxa@libero.it:
I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient.
This sounds like a rather weird setup. If the PCs are only used as ThinClients, with no local windows applications that you need, then running Windows on them is just unneccessary ballast. I would strongly recommend switching to our X2Go ThinClient image - it can be installed into an existing Windows installation, if you don't want to/cannot use network booting. Both the network booting as well as the local installation offer an easy way back to Windows if something goes wrong, as you do _not_ need to delete Windows/repartition/reformat.
At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings. Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux"
then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface.
The clean way to solve this would be the X2Go Session Broker. In broker mode, X2GoClient prompts you for your login credentials first, and determines which session tiles should be shown depending on the user name, group membership, or IP range. You'd probably want to use user name or group membership for your use case. That way, each user is only shown the tile they are supposed to see.
A hackish solution would be to specify different "sessions" files. You'd have to create two Desktop Shortcuts, each specifying --portable, and also --session-conf= - with two different "sessions" files, one per Shortcut, and each only containing one single session configuration. Then you'd use --session= to make them default to the one tile they should actually use to connect. (Using --portable on Windows will also cause a "sessions" file to be created, rather than storing the session information in the registry.)
Before going that route, I'd seriously consider an X2Go-ThinClientEditon + X2GoBroker solution, though.
In case you're afraid that it would take you too long to figure everything out yourself, the TCE build scripts are documented here (<https://wiki.x2go.org/doku.php/doc:howto:tce>), there is a demo broker environment you can install on a few virtual machines to try things out (see <https://wiki.x2go.org/doku.php/doc:howto:x2gobroker>), and if that still isn't enough, there's also the commercial support option:
<shameless plug> X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame. What makes my company special is, IMHO:
- I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me.
- As far as I know, we are the only company providing X2Go support that isn't a one-man-show.
- We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers.
Our hourly rate for consultancy work and fixing issues outside of a support contract is 125 EUR. With a support contract, you get guaranteed response times and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On Mon, Jun 25, 2018 at 9:26 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi Alaxa,
Am 25.06.2018 um 20:17 schrieb alaxa@libero.it:
I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient.
This sounds like a rather weird setup. If the PCs are only used as ThinClients, with no local windows applications that you need, then running Windows on them is just unneccessary ballast. I would strongly recommend switching to our X2Go ThinClient image - it can be installed into an existing Windows installation, if you don't want to/cannot use network booting. Both the network booting as well as the local installation offer an easy way back to Windows if something goes wrong, as you do _not_ need to delete Windows/repartition/reformat.
At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings. Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux"
then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface.
The clean way to solve this would be the X2Go Session Broker. In broker mode, X2GoClient prompts you for your login credentials first,
I think all that's asked for is a mode of x2goclient that does not display the session list on the right. Should be doable.
What I am wondering: I don't see why pyhoca session initialization should be slower than x2goclient as they are both doing the same basically.
Uli
Am 26.06.2018 um 07:11 schrieb Ulrich Sibiller:
I think all that's asked for is a mode of x2goclient that does not display the session list on the right. Should be doable.
Yes, with a 70-line bash script on the server that acts as a broker, for example. No need to duplicate functionality.
What I am wondering: I don't see why pyhoca session initialization should be slower than x2goclient as they are both doing the same basically.
It's not session initialization, but client initialization, I'd guess. Last time I tried PyHoca-GUI on Windows, it took ages to load - probably because it loads an entire Python environment into RAM first.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Thank you for reading my mind and explain better the question. Yes, I just was looking for "Username/Passowrd" fields, nothing more.
a.
Il 26 giugno 2018 alle 7.11 Ulrich Sibiller <uli42@gmx.de> ha scritto: On Mon, Jun 25, 2018 at 9:26 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote: > >Hi Alaxa, Am 25.06.2018 um 20:17 schrieb alaxa@libero.it: > > >I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient. > >This sounds like a rather weird setup. If the PCs are only used as ThinClients, with no local windows applications that you need, then running Windows on them is just unneccessary ballast. I would strongly recommend switching to our X2Go ThinClient image - it can be installed into an existing Windows installation, if you don't want to/cannot use network booting. Both the network booting as well as the local installation offer an easy way back to Windows if something goes wrong, as you do _not_ need to delete Windows/repartition/reformat. > > >At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings. Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux" then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface. > >The clean way to solve this would be the X2Go Session Broker. In broker mode, X2GoClient prompts you for your login credentials first, >I think all that's asked for is a mode of x2goclient that does not display the session list on the right. Should be doable. What I am wondering: I don't see why pyhoca session initialization should be slower than x2goclient as they are both doing the same basically. Uli _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Am 27.06.2018 um 11:05 schrieb alaxa@libero.it:
Thank you for reading my mind and explain better the question. Yes, I just was looking for "Username/Passowrd" fields, nothing more. And that's exactly what you get when you use the broker. Or the separate sessions files. See attached screenshots.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Dear Stefan,
Il 25 giugno 2018 alle 21.26 Stefan Baur <X2Go-ML-1@baur-itcs.de> ha scritto: Hi Alaxa, Am 25.06.2018 um 20:17 schrieb alaxa@libero.it: > >I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient. >This sounds like a rather weird setup. If the PCs are only used as ThinClients, with no local windows applications that you need, then running Windows on them is just unneccessary ballast. I would strongly recommend switching to our X2Go ThinClient image - it can be installed into an existing Windows installation, if you don't want to/cannot use network booting. Both the network booting as well as the local installation offer an easy way back to Windows if something goes wrong, as you do _not_ need to delete Windows/repartition/reformat.
Yes, it may sound weird but it's not: there are a lot of setups like our classroom which is based on devices like the "Wyse" from Dell. The main reason why at that moment we chose them was a better support for the RDPv10 protocol and yes, why not, a nice centralized management support. All opinable, I understand, but now that they are there we are trying to get the better experience from them; at the moment we wanted replace the "OpenNX/Nomachine" client with something newer and "x2go" seemed to be a nice option.
> >At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings.Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux" then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface. >The clean way to solve this would be the X2Go Session Broker. In broker mode, X2GoClient prompts you for your login credentials first, and determines which session tiles should be shown depending on the user name, group membership, or IP range. You'd probably want to use user name or group membership for your use case. That way, each user is only shown the tile they are supposed to see. A hackish solution would be to specify different "sessions" files. You'd have to create two Desktop Shortcuts, each specifying --portable, and also --session-conf= - with two different "sessions" files, one per Shortcut, and each only containing one single session configuration. Then you'd use --session= to make them default to the one tile they should actually use to connect. (Using --portable on Windows will also cause a "sessions" file to be created, rather than storing the session information in the registry.)
yes, that is what we are doing right now: a welcome screen with many "connectors", where each X2Go shortcut points to its own -notEditable- "session" profile. Unfortunately after one clicks it happens what I described before.
Before going that route, I'd seriously consider anX2Go-ThinClientEditon + X2GoBroker solution, though. In case you're afraid that it would take you too long to figure everything out yourself, the TCE build scripts are documented here (<https://wiki.x2go.org/doku.php/doc:howto:tce>), there is a demo broker environment you can install on a few virtual machines to try things out (see <https://wiki.x2go.org/doku.php/doc:howto:x2gobroker>), and if that still isn't enough, there's also the commercial support option:
I hoped that a compact interface was much easier than setting up another piece of software.. well, honestly THAT sounds weird to me too :-) but Ok, I may give it a try, even if and in our current setup is much more than useless :-)
<shameless plug>X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame. What makes my company special is, IMHO: 1) I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me. 2) As far as I know, we are the only company providing X2Go support that isn't a one-man-show. 3) We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers. Our hourly rate for consultancy work and fixing issues outside of a support contract is 125 EUR. With a support contract, you get guaranteed response times and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>
Ok, got it..
thank you for the kind replay and SORRY if it seemed I wanted to take profit of this list instead of going directly to the commercial support: before subscribing I read it can be used for asking help and so I did.
with regards, alaxa
Am 27.06.2018 um 09:58 schrieb alaxa@libero.it:
This sounds like a rather weird setup. If the PCs are only used as ThinClients, with no local windows applications that you need, then running Windows on them is just unneccessary ballast. I would strongly recommend switching to our X2Go ThinClient image - it can be installed into an existing Windows installation, if you don't want to/cannot use network booting. Both the network booting as well as the local installation offer an easy way back to Windows if something goes wrong, as you do _not_ need to delete Windows/repartition/reformat.Yes, it may sound weird but it's not: there are a lot of setups like our classroom which is based on devices like the "Wyse" from Dell. The main reason why at that moment we chose them was a better support for the RDPv10 protocol and yes, why not, a nice centralized management support. All opinable, I understand, but now that they are there we are trying to get the better experience from them; at the moment we wanted replace the "OpenNX/Nomachine" client with something newer and "x2go" seemed to be a nice option.
Well, X2Go-TCE offers RDP support via its FreeRDP and rdesktop backends, and we have users on Wyse/Dell hardware. So that's not a problem per se if you wanted to move away from Windows. (A word of warning, though: if you're using DisplayPort outputs, there is a known issue with certain Dell TFTs. This seems to affect not only X2Go-TCE, but all Linux versions past a certain Kernel version - the actual bug, though, is in the TFT's firmware, from what we can tell. See <https://wiki.x2go.org/doku.php/wiki:advanced:tce:tested-hardware> for more.)
At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings.Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux" then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface. >The clean way to solve this would be the X2Go Session Broker. In broker mode, X2GoClient prompts you for your login credentials first, and determines which session tiles should be shown depending on the user name, group membership, or IP range. You'd probably want to use user name or group membership for your use case. That way, each user is only shown the tile they are supposed to see. A hackish solution would be to specify different "sessions" files. You'd have to create two Desktop Shortcuts, each specifying --portable, and also --session-conf= - with two different "sessions" files, one per Shortcut, and each only containing one single session configuration. Then you'd use --session= to make them default to the one tile they should actually use to connect. (Using --portable on Windows will also cause a "sessions" file to be created, rather than storing the session information in the registry.)yes, that is what we are doing right now: a welcome screen with many "connectors", where each X2Go shortcut points to its own -notEditable- "session" profile. Unfortunately after one clicks it happens what I described before.
Not quite. You are using several session profiles, but in one and the same "sessions" file. That's the key difference. Once you start specifying separate "sessions" files, where each file contains exactly one session, you will only see one tile.
Before going that route, I'd seriously consider anX2Go-ThinClientEditon + X2GoBroker solution, though. In case you're afraid that it would take you too long to figure everything out yourself, the TCE build scripts are documented here (<https://wiki.x2go.org/doku.php/doc:howto:tce>), there is a demo broker environment you can install on a few virtual machines to try things out (see <https://wiki.x2go.org/doku.php/doc:howto:x2gobroker>), and if that still isn't enough, there's also the commercial support option:I hoped that a compact interface was much easier than setting up another piece of software.. well, honestly THAT sounds weird to me too :-) but Ok, I may give it a try, even if and in our current setup is much more than useless :-)
Well, the answer is two-fold. The Broker suggestion remains, even if you cannot move away from Windows on the client side. It will make life easier for you, once you're past the initial setup phase. And if you don't need loadbalancing (always connecting to the same X2Go server), you don't even need the "big" broker, but can use a rather simple one (which we intend to ship as a sample script in a future release, we just haven't gotten around to packaging it yet).
[commercial support]
thank you for the kind replay and SORRY if it seemed I wanted to take profit of this list instead of going directly to the commercial support: before subscribing I read it can be used for asking help and so I did.
You're always welcome to ask here - the only catch is that free support may take several days or weeks - or in the worst case, you might not get a reply at all (especially if you're asking about some edge case, particularly weird setup, or it's a holiday season).
Also, free support usually comes in the form of enabling you to help yourself - pointers to documentation, suggestions to change certain configs, etc. - so you need to be willing and able to invest some of your time in learning X2Go and doing things yourself.
Which might not be what you want to base your support on in a scenario where you're running your productions systems on X2Go, and where a failed setup means financial losses or has similar undesired effects.
With paid support, professional help is usually only a phone call or E-Mail away, and you basically turn your problem into someone else's problem, paying with money instead of your own time. Especially if you allow the support company remote access to your systems, your part of the problem solving ends at telling the supporter "Here's the broken machine, here's the money, now you go fix it."
So it's not that you _have_ to contact one of the commercial support vendors - it's just a question of whether you'd like to have more free time in exchange for paying some money. Some people actually prefer throwing money against a problem until it disappears, rather than learning new things. ;-) I know, that concept is hard to grasp for die-hard open source folks. ;-)
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
I'm using X2go-TCE on my lab full of Dell/Wyse units (D50D). They all PXE-boot to a TCE image and I have an environment setup where I can customize and rebuild the image when I need to. The wiki page documentation is a very good reference for getting it setup, but if you get stuck, please feel free to ask for assistance. I provide the regular X2go desktop as I allow users to login to one of 4 remote desktop services, but I'm sure we can get you the environment you're looking for on this platform.
Seth
On 06/27/2018 02:58 AM, alaxa@libero.it wrote:
Dear Stefan,
Il 25 giugno 2018 alle 21.26 Stefan Baur <X2Go-ML-1@baur-itcs.de> ha scritto: Hi Alaxa, Am 25.06.2018 um 20:17 schrieb alaxa@libero.it: I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient. This sounds like a rather weird setup. If the PCs are only used as ThinClients, with no local windows applications that you need, then running Windows on them is just unneccessary ballast. I would strongly recommend switching to our X2Go ThinClient image - it can be installed into an existing Windows installation, if you don't want to/cannot use network booting. Both the network booting as well as the local installation offer an easy way back to Windows if something goes wrong, as you do _not_ need to delete Windows/repartition/reformat.Yes, it may sound weird but it's not: there are a lot of setups like our classroom which is based on devices like the "Wyse" from Dell. The main reason why at that moment we chose them was a better support for the RDPv10 protocol and yes, why not, a nice centralized management support. All opinable, I understand, but now that they are there we are trying to get the better experience from them; at the moment we wanted replace the "OpenNX/Nomachine" client with something newer and "x2go" seemed to be a nice option.
At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings.Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux" then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface. The clean way to solve this would be the X2Go Session Broker. In broker mode, X2GoClient prompts you for your login credentials first, and determines which session tiles should be shown depending on the user name, group membership, or IP range. You'd probably want to use user name or group membership for your use case. That way, each user is only shown the tile they are supposed to see. A hackish solution would be to specify different "sessions" files. You'd have to create two Desktop Shortcuts, each specifying --portable, and also --session-conf= - with two different "sessions" files, one per Shortcut, and each only containing one single session configuration. Then you'd use --session= to make them default to the one tile they should actually use to connect. (Using --portable on Windows will also cause a "sessions" file to be created, rather than storing the session information in the registry.)yes, that is what we are doing right now: a welcome screen with many "connectors", where each X2Go shortcut points to its own -notEditable-
"session" profile. Unfortunately after one clicks it happens what I described before.Before going that route, I'd seriously consider anX2Go-ThinClientEditon + X2GoBroker solution, though. In case you're afraid that it would take you too long to figure everything out yourself, the TCE build scripts are documented here (<https://wiki.x2go.org/doku.php/doc:howto:tce>), there is a demo broker environment you can install on a few virtual machines to try things out (see <https://wiki.x2go.org/doku.php/doc:howto:x2gobroker>), and if that still isn't enough, there's also the commercial support option:I hoped that a compact interface was much easier than setting up another piece of software.. well, honestly THAT sounds weird to me too :-) but Ok, I may give it a try, even if and in our current setup is much more than useless :-)
<shameless plug>X2Go also has a commercial side, where various companies - including my own - offer support contracts with guaranteed response times as well as consultancy and paid-for development work if someone wants to see a bug fixed or a new feature added in a certain time frame. What makes my company special is, IMHO: 1) I'm the current X2Go Project/Community Coordinator, so the development lead and the developers tend to listen to me. 2) As far as I know, we are the only company providing X2Go support that isn't a one-man-show. 3) We sub-contract other developers from the X2Go community on demand, so you only have one person you need to talk to - me - and you will only receive one invoice, even if the task involved several freelance or part-time X2Go developers. Our hourly rate for consultancy work and fixing issues outside of a support contract is 125 EUR. With a support contract, you get guaranteed response times and lower hourly rates if you buy a certain amount of hours in advance. </shameless plug>Ok, got it..
thank you for the kind replay and SORRY if it seemed I wanted to take profit of this list instead of going directly to the commercial support: before subscribing I read it can be used for asking help and so I did.
with regards, alaxa
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
-- Seth Galitzer Systems Coordinator Computer Science Department Kansas State University http://www.cs.ksu.edu/~sgsax sgsax@ksu.edu 785-532-7790
Am 25.06.2018 um 20:17 schrieb alaxa@libero.it:
I'm sorry, i admit I wasn't clear enough. so, basically we have 30 little windows pc that act as thinclient. At the welcome screen there are the options to use "windows" or "linux" and each with a specific configration set, call it "session". So when I press "Linux" it calls the MYSESSION only with its settings. Now, I wanted to keep this welcome interface as clean and easy possible. The good was pyHoca-gui with its "username/password" window, but again, it's too slow to start once a user press "Linux"
then I saw that x2goclient can accept many parameters if run by command line and infact it works nice with the ones I specified in the previous message. Only the GUI is not "clean": it's split vertically in two parts and "worst", on the right, one can still see the name of the session. Well, it's not a drama, but it's not so clean as the pyHoca interface.
You could also use --close-disconnect, that way X2GoClient terminates after disconnecting, rather than placing you in the session tiles view.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
-
alaxa＠libero.it -
Seth Galitzer -
Stefan Baur -
Ulrich Sibiller