From owner-freebsd-bugs Tue May 30 15:20:21 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E7AD537BE3A for ; Tue, 30 May 2000 15:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA47200; Tue, 30 May 2000 15:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 30 May 2000 15:20:03 -0700 (PDT) Message-Id: <200005302220.PAA47200@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: kern/18909: select(2) timeout limited to 100000000 seconds Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/18909; it has been noted by GNATS. From: David Malone To: freebsd-gnats-submit@FreeBSD.org, archie@whistle.com Cc: Subject: Re: kern/18909: select(2) timeout limited to 100000000 seconds Date: Tue, 30 May 2000 23:15:20 +0100 Here is what "The Single UNIX Specification, Version 2" that I downloaded about a year ago says: Implementations may place limitations on the maximum timeout interval supported. On all implementations, the maximum timeout interval supported will be at least 31 days. If the timeout argument specifies a timeout interval greater than the implementation-dependent maximum value, the maximum value will be used as the actual timeout value. Implementations may also place limitations on the granularity of timeout intervals. If the requested timeout interval requires a finer granularity than the implementation supports, the actual timeout interval will be rounded up to the next supported value. So it looks the implimentation doesn't agree with this, and the man page should probably say what the max timeout is. (Excerpt is from http://www.opennc.org/onlinepubs/7908799/xsh/select.html). David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message