Is this the cause of the slow close and the underlying purpose for it?
http://www.freesoft.org/CIE/RFC/1323/24.htm
I believe most systems allow this timer to be adjusted by registry in
Windows and /proc in Linux, not sure on Mac
If the server does the bind call with SO_REUSEADDR for the listen p
I am teaching a class on Advanced network programming in C?? (nothing
web2py related) and students are reporting to me that Mac OSX takes a
long time to release a port after the program creating the socket has
been killed or crashed. The delay seems to be as large as one minute.
During this time th
Yes, this is on Mac OS X, both Leopard and Leopard Server. I am glad
it's not just me experiencing these problems.
Annet.
This is on Mac OS? I get this all the time. I see 3 things that cause
this for me (well, 4 including Ron's comment on being too quick on the
click ;) so that one was 1)
2) the socket/rocket exception I get regularly enough when i try to
open a page with "unforgivable" errors (all of which are mine
If you move too quick between pushing the stop button and hitting
start you can get the error because the server hasn't completed the
shutdown yet. I always wait a second between button presses.
On Oct 22, 3:54 am, annet wrote:
> When I do 'stop server' and 'start server' in the GUI widget, the
>
web2py is already running somewhere else. Kill all web2py processes,
and start a fresh one.
On Oct 22, 3:54 pm, annet wrote:
> When I do 'stop server' and 'start server' in the GUI widget, the
> server doesn't start, and I get this error:
>
> web2py Enterprise Web Framework
> Created by Massimo
6 matches
Mail list logo