'ifconfig tun0 destroy' gets stuck

Andriy Gapon avg at FreeBSD.org
Thu Jun 7 07:52:08 UTC 2012


on 07/06/2012 10:30 Andrew Thompson said the following:
> On 7 June 2012 19:08, Andriy Gapon <avg at freebsd.org> wrote:
>>
>> I experience a problem where vpnc can not exit cleanly and gets stuck.
>> pstree shows this chain:
>>  |-+= 31375 root vpnc
>>  | \-+- 13412 root /bin/sh /usr/local/sbin/vpnc-script-custom
>>  |   \--- 13446 root ifconfig tun0 destroy
>>
>> $ procstat -k 13446
>>  PID    TID COMM             TDNAME           KSTACK
>> 13446 102739 ifconfig         -                mi_switch sleepq_switch
>> sleepq_wait _cv_wait_unlock tun_destroy tun_clone_destroy ifc_simple_destroy
>> if_clone_destroyif if_clone_destroy ifioctl soo_ioctl kern_ioctl sys_ioctl
>> amd64_syscall Xfast_syscall
>>
>> My system is FreeBSD 10.0-CURRENT amd64 r236503.
>>
>> I think that this started happening recently but I am not sure exactly when.
>> Maybe after recent vpnc-scripts update or maybe after base system + kernel update.
> 
> This means the tun device is still open, this behavior hasn't changed
> in 3.5 years.
> 
> http://svnweb.freebsd.org/base?view=revision&revision=186391

Thank you for this pointer.  So I guess that vpnc-script just didn't do ifconfig
destroy before...

-- 
Andriy Gapon


More information about the freebsd-net mailing list