| Re: Remotely running IDL on a Mac using X11 [message #64271] |
Wed, 17 December 2008 19:33  |
Patrick V. Ford
Messages: 14
Registered: February 1997
|
Junior Member |
|
|
On Dec 17, 7:30 am, Jeremy Bailin <astroco...@gmail.com> wrote:
> On Dec 16, 9:57 pm, "pfo...@bcm.tmc.edu" <pf...@bcm.tmc.edu> wrote:
>
>
>
>> Greetings,
>
>> I am (occasionally) using IDL on a MacOS X 10.5.6, and I want to set
>> it up so a person I am collaborating with can access my Mac, which is
>> considerably more powerful than his PC laptop. I believe I have solved
>> the issues with port forwarding through my firewall/vpn box and
>> getting the Mac configured to accept the ssh –X logins.
>
>> Not being a unix person, I am now at a point where I can open a remote
>> (severe) X11 shell and enter CLI commands, but I don’t know how to
>> open/run IDL from the X11 shell and see the GUI. Some of this may be
>> due to paths being needed to be set.
>
>> I would greatly appreciate advice on how to get this functioning. It
>> is probably simple once I know.
>
>> Thanks
>
>> Patrick Ford, M.D.
>> Pfo...@bcm.tmc.edu
>
> If IDL is installed in /Applications/itt/idl, then make sure that /
> Applications/itt/idl/bin is in your path, and type:
>
> idlde
>
> (you can do "echo $PATH" to see what the path looks like... if it's
> not there, then add it with "export PATH=$PATH:/Applications/itt/idl/
> bin" if you're using a Bourne-style shell like sh or bash or "setenv
> PATH $PATH:/Applications/itt/idl/bin" if you're using a C-shell style
> shell like csh or tcsh)
>
> -Jeremy.
The path made it work on the local machine. Over my LAN, when I logged
in using ssh -X or ssh -Y, I got the following error message when I
typed in idlde:
_RegisterApplication(), FAILED TO establish the default connection to
the Window Server, _CGSDeaultConnection() is NULL.
Below is what my ssh_config file looks like. Do I need to change it?
# $OpenBSD: ssh_config,v 1.22 2006/05/29 12:56:33 dtucker Exp $
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a
comprehensive
# list of available options, their meanings and defaults, please see
the
# ssh_config(5) man page.
# Host *
# ForwardAgent no
ForwardX11 yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-
cbc,arcfour,aes192-cbc,aes256-cbc
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
Thanks
pf
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
