[Xitami] Bad termination..

[Ewen McNeill]

In message <3B7EE9E5.FE4371B8@esite-me.net>, Dan Fisher writes:
>> >Also, I have noticed lately that when I make a change to Xitami,
>> >terminate and attempt to restart, it complains that the port is already
>> >in use.  I have to reboot the machine to get to work again.
>>
>> [need to wait for connection closing timeout: netstat -nr tells you
>> if this is happening]
>
>Yes, it does show up as CLOSE_WAIT.  Is there any other way to speed up
>the closing?  

Alas, no.  It's the TCP/IP timeout.

However it only occurs (in my experience) if there are
_open_connections_ at the time that you close Xitami down; if there are
no open connections, then there's nothing to have to go through the
timeout.

So if you have the time to do it, checking for open connections 
(netstat -nr, look for connected type messages on that port), before
closing Xitami may make it easier to restart.

We'll keep this issue in mind; it maybe that there's an issue with the
way it's telling the OS "hey, it's okay to let the program restart
automatically" under some operating systems.  (Xitami does try to do
this, and it's definitely working under Linux.)

Ewen

-- 
Ewen McNeill, Technical Consultant, iMatix Corporation  www.imatix.com