Re: Possible to close a TCP/IP socket in asyn?

[Adam Bark <Adam.Bark@diamond.ac.uk>]

I didn't but disabling doesn't appear to make a difference, the local port number doesn't change so it is not reconnecting anyway.

On 23/10/14 15:25, Eric Norum wrote:

Do you have autoconnect disabled?

On Oct 23, 2014, at 5:29 AM, Adam Bark <Adam.Bark@diamond.ac.uk> wrote:

...

Thanks Mark, that certainly clarifies the situation however if I use asynCommonSyncIO::disconnectDevice (the documentation says this calls asynCommon::disconnect) the socket still shows up as "ESTABLISHED" in netstat, at least with 4-22. Am I missing some incantation? I am unclear what should go in drvPvt if I am to use asynCommon::disconnect directly.

Thanks,
Adam.

-- 
Eric Norum
eric@norum.ca

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom