X2Go Bug report logs - #1080
x2goclient should have --server option added for CLI use to specify IP of server to connect to

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: brian mullan <bmullan.mail@gmail.com>

To: submit@bugs.x2go.org

Subject: x2goclient should have --server option added for CLI use to specify IP of server to connect to

Date: Tue, 30 Aug 2016 23:18:08 -0400

[Message part 1 (text/plain, inline)]

Package: x2goclient
Version: 4.0.5.1
Severity: wishlist

*pyhoca-cli* has the *--server* option to specify the IP of the target
desktop server

but

using *x2goclient* from the CLI apparently *does not* provide that option ?

Can the --server option be added

[Message part 2 (text/html, inline)]

Message #10 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: bmullan <bmullan.mail@gmail.com>

To: 1080@bugs.x2go.org

Subject: can "--server" option to specify the IP of the target,desktop server be added to x2goclient cli

Date: Mon, 9 Jan 2017 16:24:11 -0500

the -- server option exists for pyhoca-cli but not for the x2goclient cli ?

Could it be added to provide that feature parity in the CLI ?

thanks
brian

Message #15 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: Stefan Baur <X2Go-ML-1@baur-itcs.de>

To: bmullan <bmullan.mail@gmail.com>, 1080@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#1080: can "--server" option to specify the IP of the target, desktop server be added to x2goclient cli

Date: Wed, 11 Jan 2017 00:48:53 +0100

[Message part 1 (text/plain, inline)]

Am 09.01.2017 um 22:24 schrieb bmullan:
> the -- server option exists for pyhoca-cli but not for the x2goclient cli ?
> 
> Could it be added to provide that feature parity in the CLI ?

Brian, it seems you're the only one that's particularly interested in
this feature. ;-)

That's why I doubt it'll be coming anytime soon, unless $SOMEBODY
submits a patch or offers to pay for it.

However, maybe you'd like to share why you see a use case for it? (I
doubt that "aesthetic beauty" is your only motivation for filing that
wishlist bug. ;-))
Maybe there's an easy workaround that you could use.

-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

[signature.asc (application/pgp-signature, attachment)]

Message #20 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: brian mullan <bmullan.mail@gmail.com>

To: Stefan Baur <X2Go-ML-1@baur-itcs.de>

Cc: 1080@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#1080: can "--server" option to specify the IP of the target, desktop server be added to x2goclient cli

Date: Wed, 11 Jan 2017 17:36:49 -0500

[Message part 1 (text/plain, inline)]

Hi Stefan

I'd built up a remote desktop solution for some schools where the initial
desktop was on an ubuntu cloud server.

However, on that Cloud server I had dozens of LXD containers which have a
variety of different Desktop Environments in some of them
as well as different purposes.

LXD is a "system" container technology versus the Docker type "application"
container technology.

So some of the LXD containers might be more oriented to a specific "group"
of educational users like science, or writing, or even teachers.

Those LXD containers are on their own 10.x.x.x network.

I wanted to use x2go to get to the "host" server Desktop but then just have
Desktop Icon's setup to use x2goclient cli to connect them further to a
specific LXD container Desktop of their choosing.

But although pyhoca-cli supports specifying a "- -server" target the
x2goclient cli does not include that option.

However, the x2goclient cli supports other options I wanted to use that the
pyhoca-cli does not such as "no-session-edit", "hide-menu-toolbar" etc.

My use-case problem really revolved around those kind of feature option
differences between the two CLI methods.

So I submitted the wish-list bug just to ask as not being a coder I don't
know if something is alot or a little work but there was no harm asking.

I just hadn't gotten any response.   As I know you guys are busy with the
future of Artica (btw I'm anxious to see what it is/does)... I thought I'd
just send
a ping to make sure someone at least took a look at the request.

By the way... Happy New Years to all of you guys on the x2go & artica
team(s)...!

Brian


On Tue, Jan 10, 2017 at 6:48 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:

> Am 09.01.2017 um 22:24 schrieb bmullan:
> > the -- server option exists for pyhoca-cli but not for the x2goclient
> cli ?
> >
> > Could it be added to provide that feature parity in the CLI ?
>
> Brian, it seems you're the only one that's particularly interested in
> this feature. ;-)
>
> That's why I doubt it'll be coming anytime soon, unless $SOMEBODY
> submits a patch or offers to pay for it.
>
> However, maybe you'd like to share why you see a use case for it? (I
> doubt that "aesthetic beauty" is your only motivation for filing that
> wishlist bug. ;-))
> Maybe there's an easy workaround that you could use.
>
> -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
>
>

[Message part 2 (text/html, inline)]

Message #25 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: Stefan Baur <X2Go-ML-1@baur-itcs.de>

To: brian mullan <bmullan.mail@gmail.com>

Cc: 1080@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#1080: can "--server" option to specify the IP of the target, desktop server be added to x2goclient cli

Date: Thu, 12 Jan 2017 00:12:58 +0100

[Message part 1 (text/plain, inline)]

Am 11.01.2017 um 23:36 schrieb brian mullan:

> I'd built up a remote desktop solution for some schools where the
> initial desktop was on an ubuntu cloud server.
> 
> However, on that Cloud server I had dozens of LXD containers which have
> a variety of different Desktop Environments in some of them
> as well as different purposes.
> 
> LXD is a "system" container technology versus the Docker type
> "application" container technology.
> 
> So some of the LXD containers might be more oriented to a specific
> "group" of educational users like science, or writing, or even teachers.
> 
> Those LXD containers are on their own 10.x.x.x network.
> 
> I wanted to use x2go to get to the "host" server Desktop but then just
> have Desktop Icon's setup to use x2goclient cli to connect them further
> to a specific LXD container Desktop of their choosing.
> 
> But although pyhoca-cli supports specifying a "- -server" target the
> x2goclient cli does not include that option.
> 
> However, the x2goclient cli supports other options I wanted to use that
> the pyhoca-cli does not such as "no-session-edit", "hide-menu-toolbar" etc.
> 
> My use-case problem really revolved around those kind of feature option
> differences between the two CLI methods.

Okay.  I think one way to solve this would be to install X2Go-Broker on
the host, along with postgres (the X2Go servers in the containers would
have to connect to that postgres DB as well), and have the broker
deliver the proper trimmed-down session config for the user (it can
match on user, group, IP or network range).  That way you don't have to
connect to the host desktop first.

Another, easier approach, though not as elegant, would be to configure
*all* the sessions that you need in one sessions file, then specify
either --session or --session-id on the shortcut.  Or, if you want to
use separate session configuration files, use the same name for the
session in each file, make --session point to that name, and specify the
sessions file using --session-conf.

You can also create desktop shortcuts by clicking on "Create Session
Icon on Desktop" (it's in the triangle-button -soon to be
"hamburger"-button- in the lower right of a session tile).
Have a look at the file/shortcut it puts on the desktop.

Also, in addition to using --no-session-edit, as long as your users are
sharing the same "client" system (in your case, the host to the
containers) to log on to their host, or have access to a common file
system, you can place a read-only sessions file there and use
--session-conf to point at it. Bam, central administration of the
session file, without having to install broker and postgres.

Oh, and by the way - X2GoClient has a SSH proxy feature.
So you don't have to run X2Go through X2Go to reach the container'ed
server your users are supposed to work on.
Just specify the host machine as SSH proxy in the session settings.
In that situation, you will have to make use of a shared, read-only
directory for the sessions file, though, if you want to keep
administration in a central spot.  But, if your users are all windows
users on the same network, you can even deploy the entire X2GoClient,
not only the sessions file, via a read-only network share, so you don't
even have to install it individually any more.

IMO, this isn't exactly a bug/X2Go-Dev topic any more - care to switch
over to the X2Go-User mailing list and explaining your setup further?
My hope would be that we can turn the results of this conversation both
into a success story (X2Go use at ..., by Brian Mullan) as well as a
HowTo (How to run X2Go servers in containers, with central
administration, blah, blah, blah) on our Wiki.

See
http://wiki.x2go.org/doku.php/doc:deployment-stories:start#success_stories
and
http://wiki.x2go.org/doku.php/doc:howto if you have no clue what I'm
talking about. ;-)

And of course, if you have the need for further consulting and support,
especially if you don't want to discuss your setup in public on one of
our mailing lists, we offer commercial services for that as well.
(I already feel bad for posting my "shameless plug" so often in the last
few days, so I'll refrain from it.  I'm sure you've read it often enough
if you follow the lists.)


> So I submitted the wish-list bug just to ask as not being a coder I
> don't know if something is alot or a little work but there was no harm
> asking.
> 
> I just hadn't gotten any response.   As I know you guys are busy with
> the future of Artica (btw I'm anxious to see what it is/does)... I
> thought I'd just send
> a ping to make sure someone at least took a look at the request.

It's Arctica (as in "effin' cold" ;-)), not Artica (as in artsy).  And
while some X2Go developers have left for Arctica, and others divide
their time between Arctica and X2Go, X2Go is anything but dead.

For example, Mihai is working on the macOS client, and there's also
ongoing work on what is the common base of FreeNX, NeatX, OpenNX, X2Go,
TheQVD and Arctica alike - the update/revamp of the NX-Libraries.

And while I don't exactly monitor the commit log that closely, I believe
there have been some commits by Alex (one of the two original founders
of X2Go) lately as well.

> By the way... Happy New Years to all of you guys on the x2go & artica
> team(s)...!

Thank you! :-)

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

[signature.asc (application/pgp-signature, attachment)]

Message #30 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: brian mullan <messages-noreply@linkedin.com>

To: <1080@bugs.x2go.org>

Subject: brian sent you an invitation on LinkedIn

Date: Mon, 12 Nov 2018 17:43:38 +0000 (UTC)

[Message part 1 (text/plain, inline)]

.....................................

brian would like to stay in touch on LinkedIn.

brian mullan
retired sr manager broadband advanced services at cisco systems

Sole Moderator for LXC and LXD Container Sub-Reddits

Raleigh-Durham, North Carolina Area

View profile https://www.linkedin.com/comm/in/brian-mullan-67b340135?trk=eml-guest-invite-pprofile-link-cta&trkEmail=eml-invite_guest-null-418-null-null-%7Ejmgrxf%7Ejoeljtg5%7Eyf-null-neptune%2Fprofile%7Evanity%2Eview&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3Bp3h3xqxrRqO4LwpwuyQfsQ%3D%3D

Confirm that you know brian https://www.linkedin.com/comm/start/accept-invitation?sharedKey=7RDlPwug&invitationId=6467798825166790663&trk=eml-guest-invite-cta&trkEmail=eml-invite_guest-null-416-null-null-%7Ejmgrxf%7Ejoeljtg5%7Eyf-ssuw-start%7Esignup%7Ewarm&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3Bp3h3xqxrRqO4LwpwuyQfsQ%3D%3D


.....................................

Unsubscribe: https://www.linkedin.com/e/v2?e=-jmgrxf-joeljtg5-yf&t=lun&midToken=AQFmrFVhGEd36Q&ek=invite_guest&li=426&m=unsub&ts=unsub&loid=AQFUCuWDMmJpaQAAAWcJBY-HVKG83LkzDWLe-ywQ1NlvyTCwge2UfgtTIFK_TBcy0HYg1pFwvB_6xq8BRJ6za2YGNxNiA1S5v-w&eid=-jmgrxf-joeljtg5-yf

Help: https://www.linkedin.com/e/v2?e=-jmgrxf-joeljtg5-yf&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3Bp3h3xqxrRqO4LwpwuyQfsQ%3D%3D&a=customerServiceUrl&ek=invite_guest&li=425&m=footer&ts=help&articleId=67


You are receiving Invitation emails. LinkedIn will use your email address to make suggestions to our members in features like People You May Know.

This email was sent to 1080@bugs.x2go.org.

© 2018 LinkedIn Corporation, 1000 West Maude Avenue, Sunnyvale, CA 94085. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

[Message part 2 (text/html, inline)]

Message #35 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: brian mullan via LinkedIn <invitations@linkedin.com>

To: <1080@bugs.x2go.org>

Subject: brian mullan's invitation is awaiting your response

Date: Mon, 19 Nov 2018 16:44:38 +0000 (UTC)

[Message part 1 (text/plain, inline)]

Hi ,

brian would like to connect on LinkedIn. How would you like to respond?

Accept: https://www.linkedin.com/comm/start/accept-invitation?trk=eml-email_first_guest_reminder_03-hero-21-accept_text&trkEmail=eml-email_first_guest_reminder_03-hero-21-accept_text-null-%7Ejmgrxf%7Ejoojiukm%7E7s-ssuw-start%7Esignup%7Ewarm&lipi=urn%3Ali%3Apage%3Aemail_email_first_guest_reminder_03%3B2P%2B8g%2FknRcy7rGjKhrC0og%3D%3D

View brian’s profile: https://www.linkedin.com/comm/in/brian-mullan-67b340135?trk=eml-email_first_guest_reminder_03-hero-3-prof%7Ename&trkEmail=eml-email_first_guest_reminder_03-hero-3-prof%7Ename-null-%7Ejmgrxf%7Ejoojiukm%7E7s-null-neptune%2Fprofile%7Evanity%2Eview&lipi=urn%3Ali%3Apage%3Aemail_email_first_guest_reminder_03%3B2P%2B8g%2FknRcy7rGjKhrC0og%3D%3D



.....................................

Unsubscribe: https://www.linkedin.com/e/v2?e=-jmgrxf-joojiukm-7s&t=lun&midToken=AQFmrFVhGEd36Q&ek=email_first_guest_reminder_03&li=18&m=unsub&ts=unsub&loid=AQF0_2W0hWACpQAAAWcs3A884vDFeChQ0-X9jEVaUakqd3uNLjvDIOiaT2endlpMylecpkAN3RhfUVV9JH1zkEerhqz3cDSIBnhrntY&eid=-jmgrxf-joojiukm-7s

Help: https://www.linkedin.com/e/v2?e=-jmgrxf-joojiukm-7s&lipi=urn%3Ali%3Apage%3Aemail_email_first_guest_reminder_03%3B2P%2B8g%2FknRcy7rGjKhrC0og%3D%3D&a=customerServiceUrl&ek=email_first_guest_reminder_03&li=17&m=footer&ts=help&articleId=67


 LinkedIn will use your email address to make suggestions to our members in features like People You May Know.

This email was sent to 1080@bugs.x2go.org.

© 2018 LinkedIn Corporation, 1000 West Maude Avenue, Sunnyvale, CA 94085. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.

[Message part 2 (text/html, inline)]

Message #40 received at 1080@bugs.x2go.org (full text, mbox, reply):

From: Amelia-Hollee <info3@hollee.net>

To: 1080 <1080@bugs.x2go.org>

Subject: Raincoat Supplier Since 1994--Amelia/Hollee

Date: Mon, 14 Dec 2020 09:44:32 +0000

[Message part 1 (text/html, inline)]

Send a report that this bug log contains spam.