Welcome to the new server!

[Dave]

As said before, if you're reading this, you're on the new server! Let us know of any problems in the suggestions and comments forum.

[Phi for All]

It seems much more responsive. /me likes the new server.

 

Keep Cap'n Refsmmat away from it!

[blike]

A big thanks to dave and cap'n refsmmat -- they worked hard today getting it set up so fast. This was probably the smoothest transition we've ever had.

[Cap'n Refsmmat]

This was probably the smoothest transition we've ever had.

Yeah, sorry about that. I just couldn't find a good way to make it long and painful like everyone was hoping for.

[Dave]

I guess I could rm -Rf /, that might screw things up a bit.

[doG]

I guess I could rm -Rf /, that might screw things up a bit.

 

Just make sure your never use that command unless you're logged in as root

[Mr Skeptic]

I guess I could rm -Rf /, that might screw things up a bit.

 

I've done that as root, with no bad consequences. Since I was in the root directory at the time, it refused to delete it. That said, I have no idea what it would do if you weren't in the root directory. That sort of commands are like playing Russian roulette with your computer.

[swansont]

This changed the IP address, right? My blog stats have been in the tank the last ~day, and I couldn't connect at work; that's explained by the DNS needing to catch up.

[doG]

I've done that as root, with no bad consequences. Since I was in the root directory at the time, it refused to delete it. That said, I have no idea what it would do if you weren't in the root directory. That sort of commands are like playing Russian roulette with your computer.

 

Save it as a bash script and run it with cron

[Cap'n Refsmmat]

This changed the IP address, right? My blog stats have been in the tank the last ~day, and I couldn't connect at work; that's explained by the DNS needing to catch up.

 

Yeah. They should catch up fairly quickly -- the most anyone should cache the DNS information is a day or two (even though I explicitly set the maximum cache time to 1 hour, some ISPs ignore it). I'm surprised that blog stats are in the tank though. I think the trouble is that a lot of the bots (like Google and other companies that crawl blogs) cache DNS for a reaaaally long time to save their servers some work, so it'll take them a little while.

 

If stats are still low in a few days I'd start getting worried.

[swansont]

Yeah. They should catch up fairly quickly -- the most anyone should cache the DNS information is a day or two (even though I explicitly set the maximum cache time to 1 hour, some ISPs ignore it). I'm surprised that blog stats are in the tank though. I think the trouble is that a lot of the bots (like Google and other companies that crawl blogs) cache DNS for a reaaaally long time to save their servers some work, so it'll take them a little while.

 

If stats are still low in a few days I'd start getting worried.

 

Of course, all three of those people could have just coincidentally gone on vacation

 

And/or, I just noticed the timestamp is messed up. The last entry is 2330, but right now it's 1850, so it looks like it's on UTC. It could have just dropped four hours' worth of stats, though that should have caught up yesterday.

Edited July 18, 2008 by swansont

[Cap'n Refsmmat]

I think the old server's default timezone was Central time, whereas the new uses British Standard Time. (Unless the script specifically asks for GMT/UTC, it gets the default timezone). You'll also notice that times on the forum are no longer 17 minutes slow.

[Dave]

You'll also notice that times on the forum are no longer 17 minutes slow.

 

You can thank NTP for that

[Sayonara]

That missing 17 minutes was nothing to do with the servers though; it was all down to spin gravity.

[blike]

it was all down to spin gravity.

WINNAR - A+ would read again.