Re: pgaccess failed, used to work
| От | Holger Marzen |
|---|---|
| Тема | Re: pgaccess failed, used to work |
| Дата | |
| Msg-id | Pine.LNX.4.44.0202141156030.22852-100000@bluebell.marzen.de обсуждение исходный текст |
| Ответ на | pgaccess failed, used to work (Eric Webber <streethockey@ureach.com>) |
| Список | 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
В списке pgsql-general по дате отправления: