Article View: best.migration
Article #8Watch out for "#!/usr/local/bin/perl5" in migration
From: Joe Smith
Date: Thu, 18 Oct 2001 07:53
Date: Thu, 18 Oct 2001 07:53
63 lines
3591 bytes
3591 bytes
Here's a bcc of a reply I sent to the migration team. -Joe On Wed, Oct 17, 2001 at 03:21:34PM -0600, Verio Web Migrations wrote: > Re: inwap.com > > 1. Using a browser (Netscape, Internet Explorer), go to: > http://inwap.best.vwh.net/ It looks good. Thanks for converting the #counter directives. > This is a mirrored copy of your site on the new server. Please > inspect this new site to verify everything is working correctly. It did not work at all when I first looked at it. That's because these two lines in .bhtaccess # Make "www.best.com/~inwap" go to the custom domain UserRedirect / http://www.inwap.com/ got translated to three lines in .htaccess: # WAS: UserRedirect / http://www.inwap.com/ # WAS: Redirect / http://www.inwap.com/ RewriteRule ^(.*)$ http://www.inwap.com/$1 [R] The UserRedirect directive should be completely ignored during the conversion, not translated twice into an unconditional rewrite. The new site started working when I deleted that last line. > If we don't hear from you before Tuesday, October 23 > we will assume all is well and begin the process of updating > the DNS records for your domain. Once that is complete, your > domain name will begin resolving to your new web site, and > mail will be delivered to your new web hosting account. Go ahead; I'm ready. > 2. During the migraiton period make changes to both your Best site > and the copy of your site. Otherwise when your DNS is updated your > site may not be current. > > 3. Please do not upload an old copy of your site into the new Verio > site. Instead, first download a copy and then proceed to make updates. > (FrontPage users can skip this step) If you do upload an old version > you may break portions of your site that have been migrated over. I noticed that every single one of my *.cgi or *.pl programs got renamed to file-before-migration. The first line of files that had "#!/usr/local/bin/perl" got changed to "#!/usr/local/bin/perl4", which is good. I should have identified which scripts were perl4-specific myself. But files that started with "#!/usr/local/bin/perl5" got changed to "#!/usr/local/bin/perl4". That's bad. All my perl5 scripts stopped working. I had to undo the damage by executing "mv script-before-migration script" for all the ones that had correctly being using perl5 before. -- See http://www.inwap.com/ for PDP-10 and "ReBoot" pages. -- See http://www.inwap.com/ for PDP-10 and "ReBoot" pages.
Technical Details
Message-ID:
<9qm1qn$1db2$1@nntp1.ba.best.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!news-peer-west.sprintlink.net!news.sprintlink.net!enews.sgi.com!news2.best.com!nntp1.ba.best.com!inwapShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f9f6d,941234d3c34a9844,start X-Google-Attributes: gidf9f6d,public X-Google-Thread: fdc27,941234d3c34a9844,start X-Google-Attributes: gidfdc27,public X-Google-Thread: 11488e,941234d3c34a9844,start X-Google-Attributes: gid11488e,public X-Google-ArrivalTime: 2001-10-18 00:54:10 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!news-peer-west.sprintlink.net!news.sprintlink.net!enews.sgi.com!news2.best.com!nntp1.ba.best.com!inwap From: inwap@best.com (Joe Smith) Newsgroups: best.migration,best.general,best.www Subject: Watch out for "#!/usr/local/bin/perl5" in migration Date: Thu, 18 Oct 2001 07:53:59 +0000 (UTC) Organization: Chez Inwap Lines: 63 Distribution: best Message-ID: <9qm1qn$1db2$1@nntp1.ba.best.com> NNTP-Posting-Host: shell3.ba.best.com X-Trace: nntp1.ba.best.com 1003391639 46434 206.184.139.134 (18 Oct 2001 07:53:59 GMT) X-Complaints-To: abuse@best.com NNTP-Posting-Date: Thu, 18 Oct 2001 07:53:59 +0000 (UTC)