Hello,
I have setup the x2go thin client environment. However, I'm having a few issues:
Sometimes the netboot process stops at the terminal login prompt and doesn't boot all the way into the x2goclient. How is the auto-login happening when it DOES work? Why would it be stopping sometimes at the login prompt and other times booting straight into the desktop client? Is the process run by a particular user?
When it is booting up into the fullscreen x2go client, anytime I try to make a session, it doesn't save the changes I make, thus I obviously can't login to a particular server. I put a video of the problem at http://10addyrd.com/x2gotc.mov
Is there a way to prepopulate a session for users? Where is the .x2goclient/sessions file stored that is used by x2goclient in a thin client setup?
Thanks, Neil
This e-mail and any attachments are for the intended recipient(s) only and may contain proprietary, confidential material. If you are not the intended recipient, (even if the email address above is yours) do not use, retain, copy or disclose any part of this communication or any attachment as it is strictly prohibited and may be unlawful. If you believe that you have received this e-mail in error, please notify the sender immediately and permanently delete. This email may be a personal communication from the sender and as such does not represent the views of the company.
Hi,
it's been a while since I did this, but I saved my work here: http://blog.debalance.de/?p=125
In my case, the sessions file is stored on the server as /opt/x2gothinclient/usr/share/x2goclient/sessions where /opt/x2gothinclient is my chroot.
During startup, there is a cp /usr/share/x2goclient/sessions /ramdrive/x2goclient/.x2goclient/sessions in the startup script /opt/x2gothinclient/etc/init.d/ramdrive .
The whole thinclient works on a read only nfs-root, so obviously changes cannot be saved. However, I can do temporary ones due to the ramdrive.
In my case I set x2goclient up to automatically connect to a server specified by me.
The details can be found in the script linked in my blogpost mentioned above.
Hope that helps!
Regards,
.''. Philipp Huebner <debalance@debian.org> : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F . ' HP: http://www.debalance.de, Skype: philipp-huebner
`- ICQ: 235-524-440, Jabber: der_schakal@jabber.org
Phillip,
thanks so much for the help and pointer to the script. A couple questions:
I see the /opt/x2gothinclient/etc/init.d/ramdrive script, however I don't see S*ramdrive anywhere in my /opt/x2gothinclient/etc/rc*.d directories - does this mean it isn't running at startup? If it is running at startup, how is it being executed? If not, does that mean my /ramdrive isn't even being created and mounted?
I also see in your script these lines:
chroot /opt/x2gothinclient rm -f /etc/rcS.d/S05bootlogd /etc/rcS.d/S08pcmciautils /etc/rcS.d/S09checkroot.sh /etc/rcS.d/S11checkfs.sh /etc/rcS.d/S12resize_lvm /etc/rcS.d/S16readahead-desktop /etc/rcS.d/S19portmap /etc/rcS.d/S20nfs-common /etc/rcS.d/S26cryptdisks-early /etc/rcS.d/S28cryptdisks /etc/rcS.d/S30checkfs.sh /etc/rcS.d/S45mountnfs.sh /etc/rcS.d/S46mountnfs-bootclean.sh /etc/rcS.d/S99stop-bootlogd-single /etc/rc2.d/S99stop-bootlogd
chroot /opt/x2gothinclient mv /etc/rc2.d/S20x2gothinclient /etc/rc2.d/S90x2gothinclient
It looks like you are doing some shifting of sorts on the process boot order. Can you offer any insight into what you were doing there?
-----Original Message----- From: x2go-dev-bounces@lists.berlios.de on behalf of Philipp Huebner Sent: Fri 1/21/2011 3:49 AM To: x2go-dev@lists.berlios.de Subject: Re: [X2go-dev] x2go thin client session configuration
Hi,
it's been a while since I did this, but I saved my work here: http://blog.debalance.de/?p=125
In my case, the sessions file is stored on the server as /opt/x2gothinclient/usr/share/x2goclient/sessions where /opt/x2gothinclient is my chroot.
During startup, there is a cp /usr/share/x2goclient/sessions /ramdrive/x2goclient/.x2goclient/sessions in the startup script /opt/x2gothinclient/etc/init.d/ramdrive .
The whole thinclient works on a read only nfs-root, so obviously changes cannot be saved. However, I can do temporary ones due to the ramdrive.
In my case I set x2goclient up to automatically connect to a server specified by me.
The details can be found in the script linked in my blogpost mentioned above.
Hope that helps!
Regards,
.''. Philipp Huebner <debalance@debian.org> : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F . ' HP: http://www.debalance.de, Skype: philipp-huebner
`- ICQ: 235-524-440, Jabber: der_schakal@jabber.org
This e-mail and any attachments are for the intended recipient(s) only and may contain proprietary, confidential material. If you are not the intended recipient, (even if the email address above is yours) do not use, retain, copy or disclose any part of this communication or any attachment as it is strictly prohibited and may be unlawful. If you believe that you have received this e-mail in error, please notify the sender immediately and permanently delete. This email may be a personal communication from the sender and as such does not represent the views of the company.
Hi,
On 21/01/11 18:23, Neil W. Hunt wrote:
thanks so much for the help and pointer to the script. A couple questions:
- I see the /opt/x2gothinclient/etc/init.d/ramdrive script, however I don't see S*ramdrive anywhere in my /opt/x2gothinclient/etc/rc*.d directories - does this mean it isn't running at startup? If it is running at startup, how is it being executed? If not, does that mean my /ramdrive isn't even being created and mounted?
It is the first script run by init: :~$ ls -l /opt/x2gothinclient/etc/rcS.d/S00ramdrive
lrwxrwxrwx 1 root root 18 5. Jun 2010 /opt/x2gothinclient/etc/rcS.d/S00ramdrive -> ../init.d/ramdrive
I assume this link is created from the maintainer scripts in one of the x2go thinclient packages, as well as the ramdrive script itself and so on. In my case I modified the ramdrive script a bit.
- I also see in your script these lines:
chroot /opt/x2gothinclient rm -f /etc/rcS.d/S05bootlogd /etc/rcS.d/S08pcmciautils /etc/rcS.d/S09checkroot.sh /etc/rcS.d/S11checkfs.sh /etc/rcS.d/S12resize_lvm /etc/rcS.d/S16readahead-desktop /etc/rcS.d/S19portmap /etc/rcS.d/S20nfs-common /etc/rcS.d/S26cryptdisks-early /etc/rcS.d/S28cryptdisks /etc/rcS.d/S30checkfs.sh /etc/rcS.d/S45mountnfs.sh /etc/rcS.d/S46mountnfs-bootclean.sh /etc/rcS.d/S99stop-bootlogd-single /etc/rc2.d/S99stop-bootlogd
These services don't need to run on the thinclient, I removed the startup links trying to save a little time during boot.
It would be better to use update-rc.d instead of rm -f though..
chroot /opt/x2gothinclient mv /etc/rc2.d/S20x2gothinclient /etc/rc2.d/S90x2gothinclient
It looks like you are doing some shifting of sorts on the process boot order. Can you offer any insight into what you were doing there?
I can't remember why I did this, maybe to circumvent some kind of bug due to services being started in the wrong order.
I remember e.g. kdm crashing if ntp changes the system time at a specifig time during kdm's startup.
Regards,
.''. Philipp Huebner <debalance@debian.org> : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F . ' HP: http://www.debalance.de, Skype: philipp-huebner
`- ICQ: 235-524-440, Jabber: der_schakal@jabber.org
-
Neil W. Hunt -
Philipp Huebner