[Bug 198085] service devfs restart leaks tap devices

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198085

--- Comment #1 from brian at shadowcom.net ---
/dev/tap device "instability" may have been due to sysctl setting:

root at tokyo:/etc # ls -l /dev/tap
ls: /dev/tap: No such file or directory
root at tokyo:/etc # sysctl -a | grep net.link.tap.dev
net.link.tap.devfs_cloning: 0
root at tokyo:/etc # sysctl -w net.link.tap.devfs_cloning=1
root at tokyo:/etc # sysctl -a | grep net.link.tap.dev
net.link.tap.devfs_cloning: 1
root at 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.