Sorry I cant help at all with your witango crashing issues but for the DNS swapover we have handled that in the past with having a redirect by IP.
for example we changed a domain from pointing at machine A to pointing at machine B. When we wanted to make the change, we put a redirect in place of the login screen on machine A redirecting to machine B so that right away, users started hitting machine B. When the DNS was updated, users started hitting machine B w/o being redirected from machine A first and it worked really well for us. ----- Original Message ----- From: "Roland Dumas" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, March 03, 2005 12:18 PM Subject: Re: Witango-Talk: Baling wire and duct tape to prevent crashing > > Didn't mean to send that last message to the list, but it should be obvious > by my posts that installing by the book that gets an unstable witango that > goes on for 1.5 years warrants some help. Unstable from the start. I got a > flurry of help for my first witango install, which was mostly around the > peculiarities of FMP datasources. The second install didn't get installation > support for the most serious out-of-the-box issue, witango crashing a lot. > > We're going to have to schedule a clean install of the OS and witango and > the database, etc. everything clean. Even some windex for the box. On a > production server. We'll be able to divert traffic to the dev server, which > is very stable. Just have the issue of working the TTL of the DNS, etc. so > that there aren't any orphaned transactions. > > If witango is crashy after that, it gets fired. > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
