Hi Alex,
would it be possible to allow a username override via command line option? Currently, --user is only supported in LDAP mode.
It might be a nice feature to provide the option to specify a username on the command line, overriding the username in the sessions file.
That way, one could create desktop icons (at least on Windows, but probably also on *nix) which pass the user name along, as in (for Windows): x2goclient.exe --portable --user="%USERNAME%" --session-conf="\\server\share\sessions" --session="Default" --home="%USERPROFILE%"
%USERNAME% and %USERPROFILE% are system variables on Windows, similar to $USER and $HOME on *nix.
Assuming your user names are the same on Windows and on the x2go server, this allows for one central sessions file that still automatically picks the right user name.
Sadly, this feature doesn't help me, because I'm in the unlucky position that user names are different between Windows and *nix, but maybe some other users out there could use this feature...
My workaround will probably be something along the lines of
x2goclient.exe --portable --session-conf="\\server\share\sessions.%USERNAME%" --session="Default" --home="%USERPROFILE%"
which means I will have to keep a seperate sessions file for each user, but at least I can clone it from a template.
-Stefan
Am 05.04.2012 10:12, schrieb Stefan Baur:
Hi Alex,
would it be possible to allow a username override via command line option? Currently, --user is only supported in LDAP mode.
It might be a nice feature to provide the option to specify a username on the command line, overriding the username in the sessions file.
That way, one could create desktop icons (at least on Windows, but probably also on *nix) which pass the user name along, as in (for Windows): x2goclient.exe --portable --user="%USERNAME%" --session-conf="\\server\share\sessions" --session="Default" --home="%USERPROFILE%"
%USERNAME% and %USERPROFILE% are system variables on Windows, similar to $USER and $HOME on *nix.
Assuming your user names are the same on Windows and on the x2go server, this allows for one central sessions file that still automatically picks the right user name.
Sadly, this feature doesn't help me, because I'm in the unlucky position that user names are different between Windows and *nix, but maybe some other users out there could use this feature...
My workaround will probably be something along the lines of
x2goclient.exe --portable --session-conf="\\server\share\sessions.%USERNAME%" --session="Default" --home="%USERPROFILE%"
which means I will have to keep a seperate sessions file for each user, but at least I can clone it from a template.
-Stefan
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hi Stefan,
Your request is accepted.
regards, Alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
On Tuesday 10 April 2012 11:41:39 Oleksandr Shneyder wrote:
Am 05.04.2012 10:12, schrieb Stefan Baur:
Hi Alex,
would it be possible to allow a username override via command line option? Currently, --user is only supported in LDAP mode.
This may or may not help in the short term, but I use the .ssh/config to do this sort of thing. Ofcourse this only helps if your connecting over ssh and i have no idea how windows sets this up by default. YMMV
Andrew
On 04/11/2012 01:30 AM, Andrew Mason wrote:
On Tuesday 10 April 2012 11:41:39 Oleksandr Shneyder wrote:
Am 05.04.2012 10:12, schrieb Stefan Baur:
Hi Alex,
would it be possible to allow a username override via command line option? Currently, --user is only supported in LDAP mode.
This may or may not help in the short term, but I use the .ssh/config to do this sort of thing. Ofcourse this only helps if your connecting over ssh and i have no idea how windows sets this up by default. YMMV
Andrew
Hi alex and andrew
Another option could be tampering with session files. You can specify everything in the session file, and tell the x2go client what session to use with the --session switch. I think that would be the most elegant solution
However, i don't know where x2go keeps the session files on the windows platform. On linux, it keeps them in $HOME/.x2goclient (if i remember right)
-- Venlig Hilsen / Best Regards Christoffer Krakou Fleten.net APS
Am 11.04.2012 10:35, schrieb christoffer krakou:
Hi alex and andrew
Another option could be tampering with session files. You can specify everything in the session file, and tell the x2go client what session to use with the --session switch. I think that would be the most elegant solution
No, it is not. It means keeping a bunch of sessions files, one per user, when one single file would do. A royal PITA to keep those in sync.
However, i don't know where x2go keeps the session files on the windows platform. On linux, it keeps them in $HOME/.x2goclient (if i remember right)
The default in Windows is to use the registry instead of a sessions file. This can be overridden by specifying --portable, which puts you in exactly this situation that you can either keep dozens of sessions files, or simply specify the current user with --user=%username% in a shortcut (something like a symlink on *nix, with the option to specify additional parameters). Of course, this will only work after Ales added support for --user in non-LDAP mode.
-Stefan
-
Andrew Mason -
christoffer krakou -
Oleksandr Shneyder -
Stefan Baur