From owner-freebsd-current Mon Jan 26 16:33:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27872 for current-outgoing; Mon, 26 Jan 1998 16:33:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27864 for ; Mon, 26 Jan 1998 16:33:05 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id TAA11168; Mon, 26 Jan 1998 19:31:17 -0500 (EST) Message-ID: <19980126193116.20118@rtfm.net> Date: Mon, 26 Jan 1998 19:31:16 -0500 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: select() in -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Is there any problem with select() in -current? After building a new kernel last Wednesday, a certain application has stopped working. This is a fairly reputably buggy application, however I've used it extensively without anything like this--Brian Malia has a 1/2/98 -current and says it's okay too. The nasty little critter here is XFrisk. A numerously patched XFrisk... XFrisk-0.99c0pl9+bpk2+pac3+argon4 but it doesn't matter. Anyway it will freeze and output many Warning: 22's about select() failing after the server tells it that it's its turn. It also takes 35% of the CPU, much like our friend the failing netscape (which takes more like 80% :>). Any ideas? I recompiled the binary with no success. Going to re-cvsup, maybe someone was committing while intoxicated, or yes > /usr/src'ing locally...gadzooks :-) -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net /