ssh -Y -l user etc,etc

[Eirik Byrkjeflot Anonsen]

gene heskett <gheskett at wdtv.com> writes:

> On Wednesday, February 23, 2011 04:30:52 pm Adam Jackson did opine:
>
>> On 2/22/11 11:11 AM, gene heskett wrote:
>> > Where can I find a good tutorial on making this Just Work(TM) when the
>> > user numbers are disparate, as they will be between a debian based
>> > system and the rest of the world.  I did have this working 6 months
>> > ago, but every time *buntu updates the ssh stuff on the LTS releases,
>> > it all goes away again.
>> 
>> You're going to have to be a lot more precise than that about what kind
>> of problems you're seeing.  I routinely ssh forward X connections
>> between accounts with differing UIDs on different machines, nothing more
>> complicated than ssh -Y needed.
>> 
>> - ajax
>
>
> In this case, emc is not running on the target, ubuntu machine.  I launch 
> it from this ssh -Y login, see the initial splash image, which goes away 
> after its initial timeout, and the cli then reports it couldn't get a 
> screen, so the whole thing exits.

But other X applications (e.g. xterm) works?

> The failure messages are somewhat less than worthless (to me at any rate) 
> but it does write a pair of files:

You could include the error message anyway.  Maybe they mean something
to someone.

[...]
> =================
> RUN_IN_PLACE=no
> EMC2_DIR=
[...]
> DISPLAY=axis

Hopefully this is not the X11 DISPLAY actually used by emc, but means
something else...

[...]
> Now, the fix that did make it work before is still there:
>
> gene at shop:~/emc2/configs/genes-mill$ echo $DISPLAY
> localhost:10.0

I assume you haven't set that yourself, but that it gets automatically
set by ssh?

> So, do I need to add something to this machine?  Its running pclos-32 bit, 
> 2010, uptodate except for tar as 1.24 and 1.25 are broken and will not work 
> with amanda.
>
> What happens if I change $DISPLAY to = coyote.coyote.den:10.0
> That is this machine, or I could use this machines IP too, but then either 
> marries it to this machine only, not a real fix IMO.

I assume coyote.coyote.den is the machine running the X server, rather
than the machine running emc?  Then you probably want
coyote.coyote.den:0.0, but you would need to set up proper access
controls (etc.)

eirik