From owner-freebsd-hackers Mon Sep 1 20:08:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA09822 for hackers-outgoing; Mon, 1 Sep 1997 20:08:41 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA09814 for ; Mon, 1 Sep 1997 20:08:38 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id UAA03657 for ; Mon, 1 Sep 1997 20:07:51 -0700 (PDT) Date: Mon, 1 Sep 1997 20:07:51 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@freebsd.org Subject: Select syscall Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was looking at the man page on select and some books, and I was just wondering what the would be good programming pratice when calling select in a tight look with a non-zero timeout value. Is select supposed to change the timeout value (I know that this occurs under linux to reflect time elapsed), or can you set the timeout value once and call select multiple times without fooling with it, right now I'd just assume to fill up timeout immediately before any select call, but since it is being called in an infinite for loop it would be more efficient to have it on the outside --- will this work on all BSD systems or do some change it?