Date: Sat, 28 Feb 2015 20:32:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198085] service devfs restart leaks tap devices Message-ID: <bug-198085-8-HUw1aHMzAn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-198085-8@https.bugs.freebsd.org/bugzilla/> References: <bug-198085-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198085 --- Comment #1 from brian@shadowcom.net --- /dev/tap device "instability" may have been due to sysctl setting: root@tokyo:/etc # ls -l /dev/tap ls: /dev/tap: No such file or directory root@tokyo:/etc # sysctl -a | grep net.link.tap.dev net.link.tap.devfs_cloning: 0 root@tokyo:/etc # sysctl -w net.link.tap.devfs_cloning=1 root@tokyo:/etc # sysctl -a | grep net.link.tap.dev net.link.tap.devfs_cloning: 1 root@tokyo:/etc # ls -l /dev/tap crw------- 1 root wheel 0xa9 Feb 28 15:30 /dev/tap It is this sysctl that's making the /dev/tap* devices spawn too frequently, though. (When set to zero, the "service devfs restart" command doesn't cause them to continue accumulating.) Also still unable to see /dev/tap with a glob, but as long as the program (qemu-devel) can load it by explicit name, it's not the end of the world for me. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198085-8-HUw1aHMzAn>