From: David Bear <David.Bear@asu.edu>
To: pgsql-admin@postgresql.org
Subject: long term persistent tunnels
Date: Thu, 19 Aug 2004 16:29:30 -0700
Message-ID: <20040819232930.GG23172@asu.edu> (raw)
Now that I have ssh tunneling working I am wondering what pitfalls
away.
Assume I have a server called db1 running the postgresql backend.
Asume I have another server called web1 that will be connecting to db1
for data base operations. If I setup an ssh tunnel should I be aware
of any problems with 1) spontaneously dropped connections...2) long
term time out -- 3)other?
any advice most appreciated.
--
David Bear
phone: 480-965-8257
fax: 480-965-9189
College of Public Programs/ASU
Wilson Hall 232
Tempe, AZ 85287-0803
"Beware the IP portfolio, everyone will be suspect of trespassing"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: David.Bear@asu.edu
Subject: Re: long term persistent tunnels
In-Reply-To: <20040819232930.GG23172@asu.edu>
References: <20040819232930.GG23172@asu.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox