Jonathan S. Keim wrote:
Hello,
I found the problem - a thread was erroneously closing fd 0, which
happened to be the /dev/pf file descriptor. fd 0 was subsequently being
assigned to various sockets. This would explain why ioctl(2) was
returning errno values that don't come from the PF ioctl(2)s. :)
Thanks for the brisk response, though.
On a somewhat-related note, are DIOCCOMMITRULES etc. going to be
included in 3.4 but deprecated in -current?
Yes.
My unreliable CVS tree
spider sense tells me 3.4 (and 3.4-stable) will not be receiving the
DIOCXCOMMIT and related ioctl(2) semantics.
Correct.
Cedric
