Contributed by dhartmei on from the first-poll dept.
perfectly responsive | 51.6% (263 votes) | ||
faster, but still not responsive enough | 5.9% (30 votes) | ||
slower | 2.7% (14 votes) | ||
didn't notice any difference | 39.8% (203 votes) | ||
Total votes: 510
(Comments are closed)
By Daniel Hartmeier (62.65.145.30) daniel@benzedrine.cx on
Comments
By Geert Hendrickx (81.244.145.232) geert.hendrickx@ua.ac.be on
Comments
By Daniel Hartmeier (195.234.187.87) daniel@benzedrine.cx on
Comments
By Anonymous Coward (69.197.92.190) on
Comments
By Daniel Hartmeier (62.65.145.30) daniel@benzedrine.cx on
If you have more memory to spare, Apache (with many concurrent processes forking the CGI) should be faster when there are concurrent requests. For undeadly, that happens only when we are /.ed or when many RSS readers fetch on full hours, though.
By Anonymous Coward (208.252.48.163) on
By Anonymous Coward (142.166.106.52) on
On this (new) server I get an error message rather than a hang, and here it is:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, you@your.address and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
-------------------------------------------------------------------
Apache/1.3.29 Server at undeadly.org Port 80
Comments
By Daniel Hartmeier (195.234.187.87) daniel@benzedrine.cx on
It's probably related to the HTTP headers the client provides, but I don't spot anything clearly related in the log.
Comments
By Anonymous Coward (142.166.106.52) on
http://undeadly.org/cgi?action=submit&sid=20040823084834&pid=5
This should show up in your logs as occurring at (approximately; I rarely check the accuracy of my clock) Mon Aug 23 12:49:38 ADT 2004
and from address: 142.166.106.52
If you need more detail, just post it here and I'll email you.
Comments
By Anonymous Coward (142.166.106.52) on
By Daniel Hartmeier (195.234.187.87) daniel@benzedrine.cx on
[Mon Aug 23 09:49:12 2004] [error] [client 142.166.106.52] Premature end of script headers: /htdocs/undeadly/cgi
which indicates a bug in the cgi (see Apache Server FAQ).
Could you run tcpdump -s 1600 -pXi <if> tcp port 80 and capture the HTTP request for a moderation attempt?
Comments
By Anonymous Coward (142.166.106.52) on
Comments
By Anonymous Coward (142.166.106.52) on
By Bob Beck (129.128.11.43) beck@openbsd.org on
traceroute to undeadly.org (129.128.5.155), 64 hops max, 40 byte packets
1 gateway-11 (129.128.11.1) 0.320 ms 0.309 ms 0.257 ms
2 gsb175-c4507-gsb.backbone.ualberta.ca (198.73.178.250) 0.746 ms 2.383 ms 0.811 ms
3 anchorman.srv.ualberta.ca (129.128.5.155) 0.275 ms 0.318 ms 0.271 ms
Of course, my desktop location in somewhat optimal :)
Comments
By grey (64.139.7.172) on
Seriously, if I haven't thanked you already - THANK YOU for providing the new hosting for undeadly. Not to say that Daniel running it on an old laptop from his work (which apparently doesn't have decent UPS's) was bad, because that sure was better than nothing. Thanks again!