Ross,
You rock! This works perfectly! Thank you very much!
Marc
----- Original Message -----
From: "Ross J. Reedstrom" <reedstrm@rice.edu>
To: "Marc Mitchell" <marcm@eisolution.com>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>; <pgsql-admin@postgresql.org>
Sent: Friday, September 06, 2002 9:57 AM
Subject: Re: [ADMIN] Remote monitoring
> On Fri, Sep 06, 2002 at 08:42:15AM -0500, Marc Mitchell wrote:
> > ----- Original Message -----
> > From: "Bruce Momjian" <pgman@candle.pha.pa.us>
> > To: "Marc Mitchell" <marcm@eisolution.com>
> > Cc: <pgsql-admin@postgresql.org>
> > Sent: Thursday, September 05, 2002 11:25 PM
> > Subject: Re: [ADMIN] Remote monitoring
> >
> >
> > > Marc Mitchell wrote:
> >
> > >
> > > Another option is to ssh into the machine, set your $DISPLAY back to
> > > your local machine, and then run pgmonitor. ssh does secure remote X
> > > display.
> >
> > When remote, the link between my workstation to the box being monitored
is
> > via the net where my machine gains access via a NAT router and does not
> > have its own publicly routable IP. So making the connection back from
> > server to workstation is problematic at best.
>
> I think you and Bruce are talking past each other, here. You mention
> slogin, Bruce mentions SSH. Clearly, the server can get packets to your
> workstation, and vice versa, since you can get a terminal session. SSH
> has the capability to piggy-back an encrypted X session on top of that
> connection: I don't think slogin does. To use it, you need to enable
> the option, or use the command line switch (unfortunately, the switch
> has varied from version to version of SSH, so I can't tell you which
> one it is, either -x or -X)
>
> If you've got sshd running on the server, you're golden - I do this all
> the time, with our wireless net here, BTW.
>
> Ross