From: Christopher Faylor <cgf@redhat.com>
To: overseers@sources.redhat.com
Subject: Bouncing services to the new machine?
Date: Fri, 10 Jan 2003 18:58:00 -0000 [thread overview]
Message-ID: <20030110185839.GA28398@redhat.com> (raw)
I was thinking of transitioning services to the new system on a
piecemeal basis using something like nc to redirect accesses from one
system to another.
This would obviously introduce a large lag in the connection but are
there other problems with that? I'm just a little concerned that I've
forgotten some esoteric thing on the new system which will inconvenience
people when I bring it online. If I redirect things in this way, I'll
be able to fall back to the old system quickly if the new system screws
up.
I could redirect mail, ftp, and http, I think. non-anon-cvs would be
problematic since it relies on ssh.
Anyone ever done anything like this? Bad idea? Good idea?
cgf
next reply other threads:[~2003-01-10 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 18:58 Christopher Faylor [this message]
2003-01-10 19:04 ` Ian Lance Taylor
2003-01-10 19:25 ` Jason Molenda
2003-01-10 19:40 ` Angela Marie Thomas
2003-01-10 20:35 ` Jonathan Larmour
2003-01-10 20:43 ` Christopher Faylor
2003-01-11 5:17 ` Benjamin Kosnik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030110185839.GA28398@redhat.com \
--to=cgf@redhat.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).