[X2Go-User] Is x2goserver available?
Running Linux Mint 15 (olivia), I'm trying to install x2goserver. Following directions I've updated my repository list (ppa:x2go/stable). But x2goserver does not appear as a known package. An apt-cache list on x2go only shows clients: pyhoca-cli - Command line X2Go client written in Python pyhoca-gui - Graphical X2Go client written in (wx)Python python-x2go - Python module providing X2Go client API python-x2go-doc - Python module providing X2Go client API (documentation) x2goclient - X2Go Client application (Qt4) x2goplugin - X2Go Client (Qt4) as browser plugin And of course, trying to install x2goserver fails: E: Unable to locate package x2goserver Am I missing something obvious? Thank you, - Pete ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Is x2goserver available?
Wow - Looks like I opened quite a can of worms here. How I came to be using Mint 15 is a long story, but basically when Ubuntu 10.04 (which I loved) went stale, I started looking at upgrading. Ubuntu 12 was awful, 13 was not much better. I, and several colleagues, despised the interface (Gnome, KDE, didn't matter), especially the loss (or "enhancement") of some very useful simple tools; like Alt-Tab for cycling through windows. Mint/Mate offered the closest look & feel to Ubuntu 10.04, so we started running with it. The fact that I've got 15 is probably bad luck - I started Minting just before its base (Ubuntu 13.04) went stale. Another fact: The network on which I'd run X2GO is completely private - a mix of perhaps 3 Linux/Windows systems residing on a small submarine. Could not see the wider world even if we wanted to, unless someone figures out how to propagate RF through seawater. So security is not an issue. Originally we looked at XRDB for the display porting, but was directed to X2GO as a better alternative by another colleague. That led to this discussion. BTW, I did try building X2GO directly from source, per the directions here: http://wiki.x2go.org/doku.php/sources:start But that failed miserably. Given all the options... I'll look into upgrading to Mint 17. This is tricky given the application (losing our primary control system computer for any length of time is a very bad thing), but perhaps this is the best long-term solution. At the same time - Mike I'll take you up on your offer to build a Debian package for me. I am familiar with Git, of course, but have not built .deb packages. Thanks All, - Pete Hi Peter, deb packages of X2Go Server are only available for these versions of Linux Mint: Linux Mint 13 (LTS, based on Ubuntu 12.04) Linux Mint 17 (LTS,based on Ubuntu 14.04) Linux Mint 17.1 (LTS, based on Ubuntu 14.04). I have recently tested tested 13 and 17. X2Go Server is no longer available for Linux Mint 15 because Linux Mint 15 is based on Ubuntu 13.04. The PPA no longer contains any packages for Ubuntu 13.04 and Linux Mint 13 because Ubuntu 13.04 is no longer supported. (Neither is Linux Mint 15.) Canonical actually removed the Ubuntu 13.04 packages from the PPA.[1] The packages you are seeing are packages from Ubuntu 13.04's universe repo. It should be possible to build X2Go Server, and its nx-libs dependencies, on Ubuntu 13.04 / Linux Mint 15. If you know how to use git and how to build a debian package from source, just build these: Currently 4.0.1.18: http://code.x2go.org/gitweb?p=x2goserver.git;a=shortlog;h=refs/heads/build-main Currently 3.5.0.28: http://code.x2go.org/gitweb?p=nx-libs.git;a=shortlog;h=refs/heads/build-main If you do not know how to use git or how to build a Debian package from source, then I can build them for you sometime soon. -Mike#2 [1] http://ppa.launchpad.net/x2go/stable/ubuntu/pool/main/x/x2goserver/ ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Is x2goserver available?
Sorry to dampen the drama but... Minisubs have been operating for many years with no computers whatsoever. Or simple laptops running whatever version of Windows is compatible with the sonar display. The important life-support stuff is partitioned away from all that. And Stefan, we can go offline to talk about why losing the display would not impact our ability to exercise control. Note that by "losing our primary control system" I meant any operational downtime (sitting in a warehouse) while I load a new O.S. (not in the sub itself during a dive). FYI: AUVs have been using Linux as their primary command/control O.S. for years, the only competition being Windows. The old days of dedicated realtime OS's like VxWorks or custom bare metal apps are over, except for military vehicles or maybe NASA - too expensive, too difficult to maintain. Anyway - I'm upgrading to Mint 17.1 now, so hopefully that obviates the need to build the .deb package. For those interested, here's a recent promo about the project: https://www.youtube.com/watch?v=ipAxZoMzFYk Regards, - Pete On 01/07/2015 12:10 PM, Stefan Baur wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.01.2015 um 17:42 schrieb Peter Brodsky: [...] The network on which I'd run X2GO is completely private - a mix of perhaps 3 Linux/Windows systems residing on a small submarine. Could not see the wider world even if we wanted to, unless someone figures out how to propagate RF through seawater. So security is not an issue. [...] Given all the options... I'll look into upgrading to Mint 17. This is tricky given the application (losing our primary control system computer for any length of time is a very bad thing), but perhaps this is the best long-term solution. Oh. My. God. I sure hope you know what you're doing (well, at least http://www.apl.washington.edu/people/profile.php?last_name=Brodsky&first_name=Pete seems to indicate so ;-)) and have some sort of backup/emergency control/failsafe mechanism in place that can make this thing surface automatically if something goes, forgive me the pun, belly-up. Especially if it isn't an AUV but a manned submarine. I'd probably be in for a new pair of pants and underpants if I heard the submarine I'm on is controlled by a plain off-the-shelf computer and not some sophisticated machinery with an trimmed down and hardened RTOS with a watchdog feature and a backup control system based on a different design in place. And that's not because I think X2Go is a crappy piece of software (I'm the X2Go Lead Evangelist after all, I tell people how fantastic X2Go is all the time), it's because I would never trust a regular operating system and off-the-shelf hardware for a task where human lives or some seriously expensive device like an AUV are/is at stake. That said, if you *do* get X2Go running in that environment, it would make for one heck of an entry on our success stories Wiki-page! So if you do succeed, we'd absolutely love to hear back from you! So, back to the original problem - what does "xhost" say on your current Mint 15 machines? And while this isn't exactly X2Go-related - what does the partitioning of these machines look like? If you have unpartitioned disk space, a partition you could spare (that's why I usually have a swap partition large enough to hold a small Linux installation, when changed from swap to ext, on my machines), or you are using LVM and have sufficient free space in there and a boot loader that supports booting from a logical volume, you might want to look into using debootstrap to install a newer version of your operating system into the available space, while your current installation is booted. Or, if debootstrap isn't available for Mint, do a Mint 17 install on another computer, tar the image, transfer it to a new partition/LV on the Mint 15 machine, and see if you can boot into it. That should minimize downtime. Feel free to contact me off-list for some options/best practices. My company eMail address is kont...@baur-itcs.de. I can't claim any previous experience with submarine control systems, but we do have quite a few Linux computers spread across Germany in more or less remote locations (there's even one that, according to the staff that's been on-site once to install the machine, can only be reached via horse drawn sleigh or snowmobile during the wintertime) where we do need to run upgrades with minimum downtime, and having someone on-site to perform the upgrade is usually not an option (and where it is, it tends to get expensive rather quickly), so we've come up with a few things to avoid that. At the same time - Mike I'll take you up on your offer to build a Debian package for me. I am familiar with Git, of course, but have not built .deb packages. Usually, this is the place where I would point out that
[X2Go-User] X2GO quick start (?)
Got past the Mint issue (upgraded to 17.1). Downloaded the server onto that machine, installed the client on my Windows machine. Brought up the interface the latter and - hate to sound like a dummy but... Now what? The instructions for installing are good. But at this point I'm staring at the client interface (I did set the host address and login name) and the cursor is blinking at me in the middle of the big blue square area next to the word "Session". Flame away, but what am I supposed to do now? Thanks, - Pete ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2GO quick start (?)
Doh! (How can something so obvious not be obvious?) OK - it's working. Stefan, I'll be playing with my scenario now, but if you think it would be useful for the community at large, feel free to post to the group. Thanks so much, - Pete On 01/12/2015 08:27 AM, Stefan Baur wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 12.01.2015 um 17:10 schrieb Peter Brodsky: Got past the Mint issue (upgraded to 17.1). Downloaded the server onto that machine, installed the client on my Windows machine. Brought up the interface the latter and - hate to sound like a dummy but... Now what? The instructions for installing are good. But at this point I'm staring at the client interface (I did set the host address and login name) and the cursor is blinking at me in the middle of the big blue square area next to the word "Session". Flame away, but what am I supposed to do now? If you did indeed set an address and login name (i.e. a session) correctly, you should see at least one "tile" on the right side of the X2GoClient window. If there are no tiles at all, then something went wrong during your session setup. Click on that tile, and the larger part of the window should change into a user/password login mask (unless you have a ssh private key file specified or have SSH agent authentication enabled, then it should sign you right on). BTW, I am still holding back the E-Mail you sent me off-list, with your questions regarding X2Go. As I explained, we do all unpaid support here in public on the mailing lists, so that others can learn from it, too. So if you're okay with seeing your questions on the list, just holler, and I'll forward your e-mail to the list (and will try to answer it to the best of my knowledge). - -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 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUs/YFAAoJEG7d9BjNvlEZRnYH/3aQx0tpuDx7RheABkbiGgSb dHUVAOSB6sQHmbRos2Bsau+OcSEtTTo0VVcJXbePkSOPttWU3hJyanmuLzfAiFxp 15x3drNUotCWWYrlksNi10RNIkAK/6ktAzc4Tcrkuy8SqA3Y5vPJXb0y68d0kT/x kvqk/WBWKmTF9ZfJnFXXRh687ljIARslHekRLBMPG9XgzTcMs97GFQd8DlA2QNBg 8q2SEYCD6LkqUUs3MbGtMU8PEskLviAtmhepCWlKEOiEpN+5LxqTgl/AvyPHFqpZ y8LwsYZvI/pCr1q5RTy8s3opiLCsiMFEG/YuCmH+oHPDYxnkopC70zF6D3+edrg= =DtUQ -END PGP SIGNATURE- ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user -- Peter Brodsky Principal Engineer Applied Physics Laboratory, University of Washington 1013 NE 40th St Seattle, WA 98105 brod...@apl.washington.edu 206.543.4216 ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2Go on submarine control system
>X2Go will not work with no authentication at all. However, you can use a SSH Public/Private Key pair to >authenticate, and assign no password to the private key. That way, you can automate the login and make things >work with a simple double-click on the icon. OK, indeed it will not work without authentication. Would like to try the public/private key route. I've done this for ssh agents between linux machines, using ssh-keygen to obtain the keys. Not clear how to do so w/X2GO client running under Windows. Can you provide some instructions? Thanks, - Pete ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2Go on submarine control system
No joy yet. I generated keys on the linux side: > ssh-keygen -t dsa Copied the public key to "authorized_keys" in ~/.ssh Copied the private key by sneaker-net to the Windows machine. There, I specified the latter (key file) in the field "Use RSA/DSA key for ssh connection". Then tried connecting - can't do it (tries quite a while, then times out). I did try both with and without the box "Try auto login" checked; doesn't work either way. Left the last 2 boxes unchecked. ?? - Pete On 01/12/2015 12:39 PM, Stefan Baur wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 12.01.2015 um 21:00 schrieb Peter Brodsky: X2Go will not work with no authentication at all. However, you can use a SSH Public/Private Key pair to >authenticate, and assign no password to the private key. That way, you can automate the login and make things work with a simple double-click on the icon. OK, indeed it will not work without authentication. Would like to try the public/private key route. I've done this for ssh agents between linux machines, using ssh-keygen to obtain the keys. Not clear how to do so w/X2GO client running under Windows. Can you provide some instructions? If you have access to a Linux machine, just run ssh-keygen there with the usual parameters, copy the private key file over to the Windows machine, and specify it in the session settings (there's a field where you can specify the path to an RSA/DSA key). On the Linux box, add the public key to the authorized_keys file of the user account you're trying to log in as, and you should be all set. If you want to create your key pair on Windows, you will need to use either ssh-keygen from a cygwin install, or PuttyGen.exe from the PuTTY tool suite - for the latter, you will need to use the "export" function of PuttyGen's GUI to save the private key, as PuTTY's own *.ppk key storage files are incompatible with standard ssh. - -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 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUtDDkAAoJEG7d9BjNvlEZqokH/j7m83jsuyAT+QNoywdMEy79 Ai1HH8dtC1G4pOtw1cwUerEAcGUKRZUqOn/8Fy4BMkwBZwXfvl4AU3U+GezkBEsE JraCO54ETz3LukZjNmCLO7GmU7Ql57/Dyd42CzE6wNojzD3/LwTgSZ39cC0LqGtc gghKNgSsR2A9YasKn/S2r4gfrj5nUJC3avo1fd4HLNEUunaSRykmXUXmL9gi+6oQ qjRCL/Rf2Y9EqGj5++cW1KhUG/NQPQ9pHcfvpfq/1W3Ty8lO60z7YIQ9uiHaf5qr 3wRY7ItGG1gwLHd4czKHBJ7O7cnN1IJg7UI2GMNVNcqgawgdeOgYWV43SCytFMI= =aLQz -END PGP SIGNATURE- ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user -- Peter Brodsky Principal Engineer Applied Physics Laboratory, University of Washington 1013 NE 40th St Seattle, WA 98105 brod...@apl.washington.edu 206.543.4216 ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] X2Go on submarine control system
Gentlemen, I don't know what I did differently (besides reverting to the non-Putty key, which I swear did not work before) and... Now it works. At the moment I have no need for advanced features like remote file access, sound, or printing - just the ability to run a simple Java-based GUI running on the server. And that's looking great. So - thanks so much. The support has been excellent. Now I need to document this internally before I forget it all. Best, - Pete ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Client handling of downed server
There are a couple of "features" I wonder might be addressable. For example, I mistakenly try to open a session to a (linux) server which is not powered up, the (Windows) client simply sits and tries. There's no way to cancel. Clicking on the small round on/off button in the session window (the rectangular one that lands in the left/blue area) does not take. I simply have to wait until it times out. Could this not be dealt with more actively? Obviously this is a "don't do that" kind of thing, but it does happen. Also, if the server is shut down from the client window (which is the case for us because we're effectively headless), then the client "sort of" hangs again. Trying to kill the active session window by clicking the red X in the upper right does nothing. Eventually I get a notice that the server is incommunicado and asks if I want to terminate th current session. Would be nice if there were a cleaner way to handle this. Sorry for the nitpicks - this is still a very useful tool. - Pete ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Full screen mode on client
Let me know if this is a "feature", or a bug for which I should submit a report. Running my X2Go client on a Windows 8 machine, I maximized the session window (by hitting the little square next to the red X). Now I cannot get to anything else on the client. There's no icon available to reduce or minimize the window. I tried "Esc" - no joy. Even shutting down the server doesn't help - now I have a dead session filling the screen. The only way to get out is Ctrl-Alt-Delete and kill the application. Am I missing something obvious? Thanks, - Pete ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Client handling of downed server
This is getting worse. Now, for reasons I don't understand, my client session freezes. Eventually it pops up a window saying the server is not responding and asks me if I want to terminate the session. I say yes. Nothing happens. Then I go back to the main X2Go client window and hit the "terminate" button (the round one in the lower right of the gray rectangular window inside the blue area). It asks if I want to terminate. I say yes. Nothing happens. Eventually another window pops up and tells me the server session has been killed, and indeed that window goes away. Now the client is stuck in a mode with a rotating wheel and a message "x2goclient.exe has stopped working" and a button: "Close program". I hit that button and it finally all goes away. So then I try again from scratch. Immediately get a popup: "Socket error: Unknown error". I hit OK. Hit "Cancel". Try again. Now it's hung (no message, no session). Only way to kill it is via the big red X in the upper right of the client window. - Pete On 01/14/2015 10:31 AM, Stefan Baur wrote: -BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 14.01.2015 um 19:01 schrieb Peter Brodsky: For example, I mistakenly try to open a session to a (linux) server which is not powered up, the (Windows) client simply sits and tries. There's no way to cancel. Clicking on the small round on/off button in the session window (the rectangular one that lands in the left/blue area) does not take. I simply have to wait until it times out. Could this not be dealt with more actively? Obviously this is a "don't do that" kind of thing, but it does happen. You could file a wishlist bug for that, and see if one of our volunteer devs picks up on it, or someone steps up and offers to fix it for a price. To do so, send an eMail to sub...@bugs.x2go.org, subject: something descriptive, like "add cancel button for 'connecting' phase", first two lines of the eMail must be ... package: x2goclient severity: wishlist leave one blank line after that, just like I did here, then add a description, e.g. you could just copy and paste the paragraph of your eMail that I quoted above. Also, if the server is shut down from the client window (which is the case for us because we're effectively headless), then the client "sort of" hangs again. Trying to kill the active session window by clicking the red X in the upper right does nothing. Eventually I get a notice that the server is incommunicado and asks if I want to terminate th current session. Would be nice if there were a cleaner way to handle this. Well, ordinary users should not be able to shut down the server remotely. So for our regular use cases, this isn't an issue. To shut down the server remotely, assuming you have sufficient permissions, I would suggest the following script on the server (you can place a shortcut to it on the desktop if you like), probably best stored in /usr/local/sbin/ or /usr/local/bin/: #!/bin/bash (sleep 10 && poweroff) & disown x2goterminate-session If the account you're using for X2Go remoting doesn't have sufficient permissions to run the poweroff command, I suggest installing sudo (if not already present) and setting it up in a way that your account may run "poweroff" without having to authenticate first. In that case, you need to use sleep 10 && sudo poweroff inside the brackets in the above script. (Note that I haven't tested this, but this is how it should work) The sleep 10 && poweroff tells your server to wait 10 seconds before it starts powering down. The brackets and the ampersand cause the job to run in the background. The disown tells your server to keep executing the backgrounded task even if the session disconnects. The x2goterminate-session is basically the suicide command for your running X2Go session. - -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 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUtrX5AAoJEG7d9BjNvlEZzFYIAI/tQr3s+E5p282MPpGw+PgG gFNEDtdd77hANc+ESjmFMS0jIv3aSp8zUUh2jC0IvcCp6uh0N+B8zrU2rhdVi8qP 4tS+GaA84IX9bFxhH27No9igIkrgSmD9y1UwENE/IywhlkQd+pcJumSOXoKw+RxK NnXHZaVE8oow8Uw3G2jh0tfnjwE8wSR4pCte3k0ZTfFoT2WXxOmM6wwB7EyDGTqY zO2oblaHdUN+XVppoEOcMFhtE1R1geDyPzU99Gl1cujrazE1mOQnziv88M84eVw4 +hirTPqHwbBIdBTtHN8Wu9crsibbkWel0Zv54eEkypDWia4nyXKJhiT4yfAOvFY= =E/MW -----END PGP SIGNATURE- ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user -- Peter Brodsky Principal Engineer Applied Physics Laboratory, University of Washington 1013 NE 40th St Seattle, WA 98105 brod...@apl.washington.edu 206.543.4216 ___ x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Client handling of downed server
WAIT - operator error - I had another machine w/the same static IP on the switch. Obviously a big problem. Please discount the below and I promise self-flagellation for not thinking before posting... - PB On 01/22/2015 10:29 AM, Peter Brodsky wrote: This is getting worse. Now, for reasons I don't understand, my client session freezes. Eventually it pops up a window saying the server is not responding and asks me if I want to terminate the session. I say yes. Nothing happens. Then I go back to the main X2Go client window and hit the "terminate" button (the round one in the lower right of the gray rectangular window inside the blue area). It asks if I want to terminate. I say yes. Nothing happens. Eventually another window pops up and tells me the server session has been killed, and indeed that window goes away. Now the client is stuck in a mode with a rotating wheel and a message "x2goclient.exe has stopped working" and a button: "Close program". I hit that button and it finally all goes away. So then I try again from scratch. Immediately get a popup: "Socket error: Unknown error". I hit OK. Hit "Cancel". Try again. Now it's hung (no message, no session). Only way to kill it is via the big red X in the upper right of the client window. - Pete On 01/14/2015 10:31 AM, Stefan Baur wrote: -BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 14.01.2015 um 19:01 schrieb Peter Brodsky: For example, I mistakenly try to open a session to a (linux) server which is not powered up, the (Windows) client simply sits and tries. There's no way to cancel. Clicking on the small round on/off button in the session window (the rectangular one that lands in the left/blue area) does not take. I simply have to wait until it times out. Could this not be dealt with more actively? Obviously this is a "don't do that" kind of thing, but it does happen. You could file a wishlist bug for that, and see if one of our volunteer devs picks up on it, or someone steps up and offers to fix it for a price. To do so, send an eMail to sub...@bugs.x2go.org, subject: something descriptive, like "add cancel button for 'connecting' phase", first two lines of the eMail must be ... package: x2goclient severity: wishlist leave one blank line after that, just like I did here, then add a description, e.g. you could just copy and paste the paragraph of your eMail that I quoted above. Also, if the server is shut down from the client window (which is the case for us because we're effectively headless), then the client "sort of" hangs again. Trying to kill the active session window by clicking the red X in the upper right does nothing. Eventually I get a notice that the server is incommunicado and asks if I want to terminate th current session. Would be nice if there were a cleaner way to handle this. Well, ordinary users should not be able to shut down the server remotely. So for our regular use cases, this isn't an issue. To shut down the server remotely, assuming you have sufficient permissions, I would suggest the following script on the server (you can place a shortcut to it on the desktop if you like), probably best stored in /usr/local/sbin/ or /usr/local/bin/: #!/bin/bash (sleep 10 && poweroff) & disown x2goterminate-session If the account you're using for X2Go remoting doesn't have sufficient permissions to run the poweroff command, I suggest installing sudo (if not already present) and setting it up in a way that your account may run "poweroff" without having to authenticate first. In that case, you need to use sleep 10 && sudo poweroff inside the brackets in the above script. (Note that I haven't tested this, but this is how it should work) The sleep 10 && poweroff tells your server to wait 10 seconds before it starts powering down. The brackets and the ampersand cause the job to run in the background. The disown tells your server to keep executing the backgrounded task even if the session disconnects. The x2goterminate-session is basically the suicide command for your running X2Go session. - -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 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUtrX5AAoJEG7d9BjNvlEZzFYIAI/tQr3s+E5p282MPpGw+PgG gFNEDtdd77hANc+ESjmFMS0jIv3aSp8zUUh2jC0IvcCp6uh0N+B8zrU2rhdVi8qP 4tS+GaA84IX9bFxhH27No9igIkrgSmD9y1UwENE/IywhlkQd+pcJumSOXoKw+RxK NnXHZaVE8oow8Uw3G2jh0tfnjwE8wSR4pCte3k0ZTfFoT2WXxOmM6wwB7EyDGTqY zO2oblaHdUN+XVppoEOcMFhtE1R1geDyPzU99Gl1cujrazE1mOQnziv88M84eVw4 +hirTPqHwbBIdBTtHN8Wu9crsibbkWel0Zv54eEkypDWia4nyXKJhiT4yfAOvFY= =E/MW -END PGP SIGNATURE- ___ x2go-use
