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? 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. Jon On Tue, 2003-10-07 at 13:08, Cedric Berger wrote: > Jonathan S. Keim wrote: > > >Hello all, > > > >Is it correct to say that after calling DIOCCOMMITRULES on a file > >descriptor for /dev/pf that the descriptor becomes invalid for further > >ioctl(2) rule operations? > > > > > No. > > >In particular, should I have to re-open /dev/pf after committing a > >ruleset? If I do not, all my DIOCBEGINRULES ioctl(2)s fail with EBADF > >or EOPNOTSUPP. > > > > > That's strange. Which version? > BTW: DIOCCOMMITRULES will soon disappear in -CURRENT... > It's already gone from the manpage... Use DIOCXCOMMIT. > Cedric -- Jonathan S. Keim <[EMAIL PROTECTED]> Christianity.com
signature.asc
Description: This is a digitally signed message part
