🚀 go-pugleaf

In article <9rkc8j$41b$1@nntp1.ba.best.com>,
Tom Digby  <bubbles@shell18.ba.best.com> wrote:
>When the migrated accounts were set up, our files were copied from our old
>shell directories.  So far, so good.  But some of us have modified files
>here (or added new files) since then.  One example is incoming mail
>getting saved into mbox files.

  The inbox on shell18 is ~bubbles/inbox.
  The inbox on the new system is ~bubbles/users/bubbles/INBOX.

That is, the previously copied inbox won't be touched by mail arriving
on the new server.  You can copy the most recent changes from shell18
to the new server at your leisure.  The commands I use for this are
	shell3% scp -p inbox inwap.com:
or
	inwap% rsync -e ssh -auv shell3:News .

>What will be done about those new or modified files?  Will we get a few
>days' notice after mail is redirected and before the old shell accounts
>are shut down so we can do any last-minute file salvage?

Yes.

>Or will staff copy any new or modified files across?

No.

>If staff copies the files, they should go into a new directory or an
>archive file or something so as not to overwrite any existing files in our
>migrated directories.  

Do it yourself.  Just don't overwrite the converted *.shtml or *.cgi files
unless you really mean it.

	-----------------------------------------------------

For a short period of time, I was making changes to the old
public_html/index.shtml and then having to make the same edits to the new
www/htdocs/index.shtml so as to not clobber the <!--#counter-->
directives.

Then I decided to not update http://www.best.com/~inwap anymore.
After verifying that everything was working right on the new server,
I deleted public_html/* on shell3 and left only a .bhtaccess file there
that consists of a single line:

Redirect / http://130.94.177.175/

(I had originally set it to redirect to http://inwap.best.vwh.net, but
did not want that server name to get indexed.  I tried setting it to
http://www.inwap.com/ 48 hours after the DNS change over, but noticed in
the log files that some browsers from the UK were using DNS servers that
still hadn't gotten the new IP address, producing an infinite loop of
redirects back to the virtual host on www3.ba.best.com.)

I plan to leave the numeric IP address there for a week or so.
I expect that another mechanism will be in place to redirect
http://www.best.com/~inwap to http://www.inwap.com once my access to
shell3 is ended.
	-Joe
--
See http://www.inwap.com/ for PDP-10 and "ReBoot" pages.