I don't know what's going on, but this new server seems
not to like me at all.

I have been virtually unable to
use this account, though I can log in as perlbot
normally. At first it seemed that I could not log on at
all, but with experimentation I discovered that lynx
would sometimes get through if allowed to try for five
minutes or so. I wound up attempting to log in with 8 lynx
sessions from various servers... three have allowed me to
log in so far... only this one has gotten me far enough to
post. This has taken well over an hour... so I have to say, in my experience, this server is "slower". ;-)

Clearly this is not a cookie problem, as others have had; the phenomenon is connected to the account, and must be on the server side. If someone (vroom, maybe) would be kind enough to help me out, I'd much appreciate it. I'm going through CB withdrawl. ;-(

I have a 1.54Mbps cable connection and an 850MHz CPU
(effectively removing all other bottlenecks) and the
site definitely seems more responsive. After the screen
refreshes there's almost no delay before showing the page.
Before you would have to wait a bit as the browser
reported "Contacting host..." or "Loading..." although
it's possible that was due to the remote banner ads and
not necessarily the server.

At any rate... I don't know what will happen in the
future, as the server's RAM fills up and more users start
hitting the site, but for now: Nice work! {g}

It seems to have broken my bookmarks somehow - i'm trying to figure that out now. but i have bookmarked things like Newest Nodes and Best Nodes and those bookmarks do not work now. They didn't refer to IP so I'm stumped about it...

"A man's maturity -- consists in having found again the
seriousness one had as a child, at play." --Nietzsche

Your bookmarks should work again after DNS gets updated/propagated with the new box's IP address. Essentially the same reason why cookies need reissued - issueing server was www.perlmonks.org, but the new box is (temporarily) just 206.170.14.76 with no DNS name.

At least, that's been my experience the other couple times His Vroomness moved PM since I've been here.

Update: As merlyn points out below, www.perlmonks.org is, for the moment anyway, just a redirect from old box to the new box's IP address. I wouldn't be too concerned - vroom has always been waaay more responsive than any could ask for. Doubtless things will be back to normal in no time.
cheers,
Don
striving for Perl Adept(it's pronounced "why-bick")

No doubt vroom will fix all of this...saw it was redirect soon after posting. I just figured this poll was trying to draw any and all things seen different since the move. Far be it from me to think I know enough to know what problems are big or small =)

"A man's maturity -- consists in having found again the
seriousness one had as a child, at play." --Nietzsche

I don't know if this is temporary, but a link like
/?node_id=42739 used to work but as of this writing, that link gets a mostly blank page. To get the link to work, I now have to resort to
/index.pl?node_id=42739. I think the default page needs to be changed from "index.html" to "index.pl". This will become even more important when the DNS change hits as http://www.perlmonks.org/ isn't going to be very interesting any more. (:

I would have thought this type of change would have been easier to do by changing the IP address of the computer and changing any internal DNS entries if the machine goes by a name other than "perlmonks". But I'm not in on the details.

I can't say I've ever tried it but I think 404 pages (which the old perlmonks will give from bookmarks) will have the requested URL as their document.href in JavaScript. So a autodirecter could be written to redirect www.perlmonks.org/foo/bar to 206.170.14.76/foo/bar.I think so, anyway. -- Dave

Yummy new server. Ate my cookie, took me three tries before I remembered that my username was capitalized. If that was done by one of my users, I'd be forced to <clickity><click> them, so I guess I'll have to cut someone a break today. 8)

Running great for me... quite zippy. No problems logging in; overall very responsive here on my cable modem. Not too shabby considering I'm 20 hops out, and half of those are going through the (usually spotty) sprintlink network. All in all, couldn't be running better from what I can see.