Question #213734 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/213734
Charles Howardandsware gave more information on the question: Update ---------- Focusing on the epoptes-client command not working; I could see from the error message that 'socat' was being called by 'epoptes-client' and 'socat' wasn't happy with it's parameters. I have no idea how 'epoptes-client' is calling 'socat' or how to find out. So I looked where I could. I inspected the environement variables on each client. There were differences but nothing stood out. So I decided to run the 'epoptes-client' command again on each client desktop to see if comparing the socat message with the output from the working session gave any info'. I noticed that the working session said:- * Epoptes-client connecting to localhost:789 Whereas the x2go session said:- * Epoptes-client connecting to server:789 Given that 'locahost' is a valid address and 'server' isn't unless it's been set somewhere. Given also that 'server not known' appears in the error message. I decided to try passing in 'localhost' as a parameter to the 'epoptes-client' call. It turned out to be straight forward enough:- $ epoptes-client localhost And it worked. The question now is: how to fix the 'epoptes-client' call to socat when a x2go session logs in? What exactly needs fixing and where? Does this problem lie within my epoptes installation? or x2go? or somewhere in the Edubuntu installation? Any suggestions gratefully received. -- You received this question notification because you are a member of Epoptes Developers, which is an answer contact for Epoptes. -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
