connect-script double call

Steve steve at thupdi.net
Sun Apr 13 13:32:42 PDT 2014


Update: be3920a08cdc561f01f9ac5f995441e7408bea18

The VPN devices keeping in system, vpn1 vpn2 vpn3 ..

Disconnect doesn't kill device.



On Sun, Apr 13, 2014 at 2:31 PM, Steve <steve at thupdi.net> wrote:
> Thanks for the work. The new improvement works with the first
> connection, the second and next connections now always fail with
> error:
>
> "Connection attempt has failed due to server communication errors."
>
> On Sun, Apr 13, 2014 at 6:15 AM, Nikos Mavrogiannopoulos
> <nmav at gnutls.org> wrote:
>> On Sun, 2014-04-13 at 00:40 +0800, Steve wrote:
>>> Hi, Nikos
>>>
>>> Still not work: vpns1: error fetching interface information: Device not found
>>>
>>> Only the first disconnect could gather info from the device, the next
>>> disconnections never do it.
>>
>> There is a race condition there. As the script runs into the background
>> there can be that the device is closed prior to the script accessing it.
>> I've now modified the worker process cleanup to involve an extra
>> transition to state dead prior to complete cleanup. That should give
>> time for the script to execute.
>>
>> regards,
>> Nikos
>>
>>



More information about the openconnect-devel mailing list