From owner-freebsd-hackers Wed Jan 6 16:03:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26891 for freebsd-hackers-outgoing; Wed, 6 Jan 1999 16:03:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26812 for ; Wed, 6 Jan 1999 16:03:21 -0800 (PST) (envelope-from dwhite@pond.net) Received: from localhost (dwhite@localhost) by guppy.pond.net (8.8.8/8.8.7) with SMTP id PAA22821; Wed, 6 Jan 1999 15:51:23 -0800 (PST) Date: Wed, 6 Jan 1999 15:51:23 -0800 (PST) From: Doug White To: Graham Wheeler cc: hackers@FreeBSD.ORG Subject: Re: bpf select() broke? In-Reply-To: <199901060852.KAA00920@cdsec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Jan 1999, Graham Wheeler wrote: > > Do Berkeley packet filter devices (/dev/bpfX) supposed to respond like > > normal files and devices to a select() system call? > > > > My experimentation (based on 2.2.7-RELEASE) shows that they don't. They > > don't return when they have data waiting to read and they don't return > > when they're ready to be written to. The bpf fd is definitely in the fd > > list going into the select(), so don't try to pin pilot error on this one. > > We use select on read on BPF devices for all our BPF code on 2.2.7, and it > works for us. Select on write definitely doesn't work (it isn't implemented). Select on write doesn't work, eh? I'll try that. Thanks for the information! Doug White | Pacific Crest Networks Internet: dwhite@pond.net | http://www.pond.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message