From: | Holger Marzen <holger(at)marzen(dot)de> |
---|---|
To: | tony <tony(at)animaproductions(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgaccess failed, used to work |
Date: | 2002-02-14 10:57:43 |
Message-ID: | Pine.LNX.4.44.0202141156030.22852-100000@bluebell.marzen.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 14 Feb 2002, tony wrote:
> On Thu, 2002-02-14 at 07:45, Holger Marzen wrote:
>
> > It seems that you did a "su" or "telnet" to your local or another
> > machine and then started pgaccess. Either your DISPLAY variable isn't
> > correct (it should be something like 192.168.0.3:0 - ipaddress of the
> > machine where your X-server runs and a display number, eg 0 for the
> > first X-server) or you forgot to issue a "xhost +xxx" where xxx is the
> > name or the ip address of the machine running pgaccess.
> >
> > It is no pgaccess problem. xclock won't work, either. I recommend using
> > ssh with enabled X11-forwarding, that does the job of setting DISPLAY
> > and permissions automagically.
>
> And via ssh? I can't ssh into the machine running pgaccess (port 22 on
> the router is forwared to my server) so I ssh into the server then into
> the workstation.
>
> Any clues on the DISPLAY variable to give for that???
It is usually done automagically. Be sure to turn X11 forwarding on, in
every ssh_config and every sshd_config.
--
PGP/GPG Key-ID:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xB5A1AFE1
From | Date | Subject | |
---|---|---|---|
Next Message | Bjoern Metzdorf | 2002-02-14 12:32:23 | Replication (sigh) |
Previous Message | Jairo Tcatchenco | 2002-02-14 10:55:51 | In Oracle, synonym, in pgsql, ... |