10001110100110101
Morning! Any triskaidekaphobics here? I just got word that Scour has filed for bankruptcy! Doh! Where am I going to get my MP3s from now? Okay, so I haven't gotten any MP3s from them in a long, long time (they took them down ages ago). I first saw this on the ShackNews.
Ouch. I hope nobody out there owns any tech stocks. They got hammered recently. (My stocks are only worth what I paid for them now.) On another note, this is also a good time to buy.. *checks* Oops. Too late, people are buying already.
On the update front, we've got Laz who's been playing around with his page, and KGL who's complaining (as always =).
I guess I should go and take a shower now huh?
Friday, October 13, 2000 at 18:57:21 (UTC)
About your remote script speed, do you know if HostnameLookups and/or IdentityCheck(or their nearest non-Apache equivalent) is turned on on your server? It seems like something has to timeout before data is sent. This is the only thing I can think of if the scripts are fine locally.
FlyingS
Friday, October 13, 2000 at 21:04:01 (UTC)
Actually, the server does do a hostname lookup. But not all of the scripts take note of the host names however, or does this matter?
A better question would be: How do you fix it?
QYV
Monday, October 16, 2000 at 15:48:24 (UTC)
Yup, it matters. Any time you run a script with that HostnameLookups on, the CGI module will try to find the hostname of the client so it can populate the REMOTE_HOST environment variable, whether you read that variable or not. That's (usually) unnecessary overhead.
Looks like the only thing you can do about it is mail your sysadmin and ask for HostnameLookups to be disabled. S/he can do it for your directory only if s/he's using it for something. It might not solve the problem, but it would seem to me to be the most likely culprit.
FlyingS