Date: Mon, 2 Oct 2000 13:11:04 -0700 (PDT) From: "Ronald F. Guilmette" <rfg@monkeys.com> To: FreeBSD-gnats-submit@freebsd.org Cc: rfg@monkeys.com Subject: docs/21708: kqueue/kevent man pages isn't specific about `timeout' Message-ID: <200010022011.e92KB4o79506@monkeys.com>
next in thread | raw e-mail | index | archive | help
>Number: 21708 >Category: docs >Synopsis: kqueue/kevent man pages isn't specific about `timeout' >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 02 13:20:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 4.1-RELEASE i386 >Organization: Infinite Monkeys & Co. >Environment: >Description: The man page for kqueue/kevent doesn't explicitly say what the semantics of the `timeout' parameter for the kqueue(2) function are. Will a call to kqueue() timeout and return to the caller (with a return value of zero) when no currently-monitored events have occured for the amount of _elapsed_ time specified by the `timeout' parameter? Or will a call to kqueue() timeout and return to the caller (with a return value of zero) if no monitored events have occured by the time the system's own clock says that we have reached the time specified by the `timeout' parameter? In short, is the `timeout' parameter for kevent(2) interpreted (by the kernel) as a _relative_ time period, or as an _absolute_ time specification? The kevent(2) man page does not make this clear. >How-To-Repeat: RTFManpage >Fix: Specify in the manpage that `timeout' is either (a) relative or else (b) absolute. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010022011.e92KB4o79506>