Date: Thu, 7 Jun 2012 19:30:13 +1200 From: Andrew Thompson <thompsa@FreeBSD.org> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-net@freebsd.org, Emanuel Haupt <ehaupt@freebsd.org> Subject: Re: 'ifconfig tun0 destroy' gets stuck Message-ID: <CAFAOGNRdGCG67mZ0s=Hdfha7aR-s9JYjQDu1QYUDyxx3yaHSQg@mail.gmail.com> In-Reply-To: <4FD0537C.7070802@FreeBSD.org> References: <4FD0537C.7070802@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 June 2012 19:08, Andriy Gapon <avg@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 Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFAOGNRdGCG67mZ0s=Hdfha7aR-s9JYjQDu1QYUDyxx3yaHSQg>