Prev: Sudden X11 forwarding glitch - Can't open display "localhost:10.0"
Next: slack64 and /lib32 missing ?
From: Joost Kremers on 10 Feb 2010 12:32
Mike Jones wrote:
> On the client box...
> $CLIENT ssh $SRVR
> $SRVR echo $DISPLAY
>
> $
>
> I just got a blank line on the RXVT I sshed to the SRVR on.
>
> This looks wrong.

try ssh -Y $SRVR

that should give you something like 'localhost:10.0'.

and even though i don't understand why it says 'localhost' (the display, after
all, is not on the machine one is logged into), it does seem to be correct.


--
Joost Kremers joostkremers(a)yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
From: Mike Jones on 10 Feb 2010 19:20
Responding to Joost Kremers:

> Mike Jones wrote:
>> On the client box...
>> $CLIENT ssh $SRVR
>> $SRVR echo $DISPLAY
>>
>> $
>>
>> I just got a blank line on the RXVT I sshed to the SRVR on.
>>
>> This looks wrong.
>
> try ssh -Y $SRVR
>
> that should give you something like 'localhost:10.0'.
>
> and even though i don't understand why it says 'localhost' (the display,
> after all, is not on the machine one is logged into), it does seem to be
> correct.


Should, but doesn't.

It all seems to hang on that one single detail, something isn't seeing
\getting access to localhost:10.0

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Mike Jones on 11 Feb 2010 04:55
Responding to Grant:

> On Thu, 11 Feb 2010 00:20:55 GMT, Mike Jones <Not(a)Arizona.Bay> wrote:
>
>>Responding to Joost Kremers:
>>
>>> Mike Jones wrote:
>>>> On the client box...
>>>> $CLIENT ssh $SRVR
>>>> $SRVR echo $DISPLAY
>>>>
>>>> $
>>>>
>>>> I just got a blank line on the RXVT I sshed to the SRVR on.
>>>>
>>>> This looks wrong.
>>>
>>> try ssh -Y $SRVR
>>>
>>> that should give you something like 'localhost:10.0'.
>>>
>>> and even though i don't understand why it says 'localhost' (the
>>> display, after all, is not on the machine one is logged into), it does
>>> seem to be correct.
>>
>>
>>Should, but doesn't.
>>
>>It all seems to hang on that one single detail, something isn't seeing
>>\getting access to localhost:10.0
>
> Unclean shutdown? Did you check for lock files(/var/lock/, var/run/,
> /etc/??) can't remember where else they're kept.
>
> Grant.


Not thought of that. Just checked and everything seems clean enough.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Bit Twister on 11 Feb 2010 16:17
On Thu, 11 Feb 2010 21:52:30 +0100, Martin Schmitz wrote:
> Bit Twister wrote:
>> $ get_wan_ip.pl
>> 71.170.056.46
>> $ get_wan_ip.pl
>> 24.117.051.251
>> $ env | grep 170.056
>> SSH_CLIENT=71.170.056.46 44543 22
>> SSH_CONNECTION=71.170.056.46 44543 24.117.051.251 22
>
> These are really strange representations of ip addresses, by the way. I
> guess that many programs aren't able to handle them the right way. A '0'
> at the beginning of an octet means that it's an octal digit.
>
> So these addresses SHOULD be written 71.170.46.46 and 24.117.41.251.
> Look what ping does:
>
> [dakini]~# ping 71.170.056.46
> PING 71.170.056.46 (71.170.46.46) 56(84) bytes of data.
> 64 bytes from 71.170.46.46: icmp_seq=1 ttl=53 time=189 ms
>
> In contrast 'ipcalc' isn't able to interpret it right:
> [dakini]~# ipcalc 71.170.056.46
> Address: 71.170.56.46 01000111.10101010.00111000. 00101110
>
> So maybe this has something to do with your problem...?

Not really. I was munging the ip addresses. I have no problems.
Just giving a working example.
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Sudden X11 forwarding glitch - Can't open display "localhost:10.0"
Next: slack64 and /lib32 missing ?