From owner-freebsd-hackers Tue Jan 5 14:25:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19931 for freebsd-hackers-outgoing; Tue, 5 Jan 1999 14:25:29 -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 OAA19916 for ; Tue, 5 Jan 1999 14:25: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 OAA14612 for ; Tue, 5 Jan 1999 14:13:50 -0800 (PST) Date: Tue, 5 Jan 1999 14:13:50 -0800 (PST) From: Doug White To: hackers@FreeBSD.ORG Subject: bpf select() broke? 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 Hello all ... I'm posting this again since I didn't get much reply last time, and I hope to cull the BPF-meister from his hole ... 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. The code in /sys/net/bpf.c appears to support it but since I'm no kernel hacker I'm not going to trace what's going on, at least not yet. I'll try compiling my code on a relatively CURRENT box at home, but I'm not sure it's set up enough to fully test the condition. Thanx for any help. 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