Original Message
From: "Arno Garrels" [EMAIL PROTECTED]
> BTW: FreeCurrentPasvPort is called multiple times in most cases, doesn't
> hurt,
> but's not very nice.
That's true - however all calls do have their reason - (just like the one
call to FreeCurrentPasvPort we just added (won't
Peter Feldbaumer wrote:
>
> In TFTPServer.WMFtpSrvClientClosed() the following two lines have to be
> added, best would be just before FClientList.Remove(Client);
That makes sence ;-)
BTW: FreeCurrentPasvPort is called multiple times in most cases, doesn't hurt,
but's not very nice.
Arno
>
Original Message
From: "Arno Garrels" <[EMAIL PROTECTED]>
> I'm using current version of the ICS-SSL distribution and I'm testing
> with the official demo application having SSL enabled.
This should definitely be fine...
> I changed and tested different shutdown procedures in WSocket.pa
"Peter Feldbaumer" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Tuesday, January 17, 2006 12:15 AM
Subject: Re: [twsocket] Ftp server FreeCurrentPasvPort
>
> > While I'm testing ICS-SSL shutdown stuff.
> > FreeCurrentPasvPort of FTP server is
Peter Feldbaumer wrote:
>> While I'm testing ICS-SSL shutdown stuff.
>> FreeCurrentPasvPort of FTP server is either not working properly or
>> it is not always called, no idea, however if it once triggered error
>> "no available passive ports" (or something like that), you can wait for
>> ever,
> While I'm testing ICS-SSL shutdown stuff.
> FreeCurrentPasvPort of FTP server is either not working properly or
> it is not always called, no idea, however if it once triggered error
> "no available passive ports" (or something like that), you can wait for
> ever, even until there's no more
Hi,
While I'm testing ICS-SSL shutdown stuff.
FreeCurrentPasvPort of FTP server is either not working properly or
it is not always called, no idea, however if it once triggered error
"no available passive ports" (or something like that), you can wait for
ever, even until there's no more socket
