For what it's worth it might be better to make it dependent upon/bin/sh rather than bash. It must only need those facilities since it works with different supersets of /bin/sh, and /bin/sh is ubiquitous, where as bash may not be present on some more anitique Unixes (though it will compile on anything, I've even got it compiled on an antique Sun SS-10 running SunOS 4.1.4)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 5 May 2015, Mihai Moldovan wrote:
Date: Tue, 05 May 2015 03:02:28 +0200 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] Keyboard Translation Mac/OS
On 05.05.2015 02:57 AM, Robert Dinse wrote:
What seems odd to me is that if I originate from a Ubuntu machine, withcsh as the shell on the target host, it works. It only breaks if originated from a Mac.
That's because the command chain is only executed by the OS X version of X2Go Client. Sorry if I was unspecific about that. xmodmap is *not* executed on Linux or Windows, so the "problematic" command is never run through X2Go Client on these platforms.
The whole call is doomed anyway, because it's doing something like # echo "HUGE LIST OF XMODMAP OUTPUT FROM THE OS X CLIENT MACHINE" | xmodmap -
Now of that huge list by chance includes a quote character, the fun begins.
It would seem there should be some way to separate the shell x2go uses to process commands, i.e., explicitly invoking /bin/bash instead of just assuming it's what will process the commands, for instances where users are using something else.
That's one solution, yep. Not sure why the code is currently not doing that, though. It would add another dependency on bash, but would make things (not only for that problem, but in general!) *a lot* more deterministic. Thanks.
Ksh is a superset of bourne shell as is bash so that's probably why it has enough in common to work.
Exactly.
Mihai