On 11 Jun 2008, at 22:04, Gunnar Wolf wrote:
Granted, we cannot expect much configurability from the configurator,
right? :-) The choice of port 4000 is IMHO unfortunate, as it is a
common port for local use. And it is not documented at all. But the
real problem is the conflict is not reported - The user just gets a
«500 Internal Server Error» message, but nothing in the console.
Yeah, it was a bug, indeed. The good news is that it is now fixed
(r1534) in trunk and the 0.7 branch.
Would any of you feel like coding a
failover mechanism, that looks for a free port? I am completely
unfamiliar with the mechanism, so I'd rather ask for a patch than
write one myself ;-)
Hehe.. of course, you have two wishes left. :)
http://svn.cherokee-project.com/changeset/1534#file2
So, of course, this is just matter of anticipating we will be
terminated by a Ctrl-C, avoiding a head-scratching user ;-) So, would
anybody object to this? (I'm submitting it to the list as I'm a
complete python newbie, and I don't grok cherokee internals)
It's applied now in trunk and the 0.7 branch:
http://svn.cherokee-project.com/changeset/1535#file1
Thanks a million for the report and the patch!
PS: I will release 0.7.2 tomorrow so we can get the patched version in
Debian on time.
--
Greetings, alo.
http://www.alobbs.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
