From owner-freebsd-standards@FreeBSD.ORG Mon Aug 4 11:07:03 2008 Return-Path: Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42E551065676 for ; Mon, 4 Aug 2008 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 332648FC15 for ; Mon, 4 Aug 2008 11:07:03 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m74B73AK082218 for ; Mon, 4 Aug 2008 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m74B725m082214 for freebsd-standards@FreeBSD.org; Mon, 4 Aug 2008 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Aug 2008 11:07:02 GMT Message-Id: <200808041107.m74B725m082214@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-standards@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2008 11:07:03 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/25542 standards sh(1) null char in quoted string o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/82654 standards C99 long double math functions are missing o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat 5 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s bin/14925 standards getsubopt isn't poisonous enough o stand/21519 standards sys/dir.h should be deprecated some more o bin/24390 standards ln(1) Replacing old dir-symlinks when using /bin/ln s stand/24590 standards timezone function not compatible witn Single Unix Spec o stand/25777 standards [kernel] [patch] atime not updated on exec a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s s stand/36076 standards Implementation of POSIX fuser command o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings p stand/41576 standards POSIX compliance of ln(1) o stand/44425 standards getcwd() succeeds even if current dir has perm 000. o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/54833 standards [pcvt] more pcvt deficits o stand/54839 standards [pcvt] pcvt deficits p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int o stand/56476 standards cd9660 unicode support simple hack o stand/58676 standards [patch] grantpt(3) alters storage used by ptsname(3) s stand/62858 standards malloc(0) not C99 compliant s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- o stand/70813 standards [PATCH] ls(1) not Posix compliant o stand/72006 standards floating point formating in non-C locales o stand/79056 standards [feature request] [atch] regex(3) regression tests a stand/80293 standards sysconf() does not support well-defined unistd values o stand/81287 standards [PATCH]: fingerd(8) might send a line not ending in CR o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm a stand/86484 standards [PATCH] mkfifo(1) uses wrong permissions o stand/92360 standards [headers] [patch] Missing TAB3 in kernel headers o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/96016 standards [headers] clock_getres et al should be in o stand/96236 standards [PATCH] [POSIX] sed.1 incorrectly describes a function p stand/99517 standards Missing SIGRTMIN and SIGRTMAX signals o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o kern/114578 standards [libc] wide character printing using swprintf(dst, n, o stand/116081 standards make does not work with the directive sinclude o stand/116221 standards [kernel] [patch] [request] SUS issue -- FreeBSD has no o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116826 standards [PATCH] sh support for POSIX character classes o stand/118047 standards SUGGESTION: /etc/printcap vs mergemaster o stand/119804 standards [timedef] [patch] Invalid (long)date format in pl_PL.I o stand/120947 standards xsm ignores system.xsm and .xsmstartup o stand/121568 standards [patch] ln(1): wrong "ln -s" behaviour o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o bin/125855 standards sh(1) allows for multiline, non-escaped control struct 49 problems total. From owner-freebsd-standards@FreeBSD.ORG Mon Aug 4 14:12:08 2008 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 077431065690; Mon, 4 Aug 2008 14:12:08 +0000 (UTC) (envelope-from das@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D63E48FC12; Mon, 4 Aug 2008 14:12:07 +0000 (UTC) (envelope-from das@FreeBSD.org) Received: from freefall.freebsd.org (das@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m74EC7sS004661; Mon, 4 Aug 2008 14:12:07 GMT (envelope-from das@freefall.freebsd.org) Received: (from das@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m74EC72M004657; Mon, 4 Aug 2008 14:12:07 GMT (envelope-from das) Date: Mon, 4 Aug 2008 14:12:07 GMT Message-Id: <200808041412.m74EC72M004657@freefall.freebsd.org> To: timur@gnu.org, das@FreeBSD.org, freebsd-standards@FreeBSD.org From: das@FreeBSD.org Cc: Subject: Re: standards/99517: Missing SIGRTMIN and SIGRTMAX signals X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2008 14:12:08 -0000 Synopsis: Missing SIGRTMIN and SIGRTMAX signals State-Changed-From-To: patched->closed State-Changed-By: das State-Changed-When: Mon Aug 4 14:10:05 UTC 2008 State-Changed-Why: As stated nearly two years ago, realtime signal support is unlikely to be MFCed to RELENG_6. You'll find SIGRTMIN and SIGRTMAX in 7.0 and later. http://www.freebsd.org/cgi/query-pr.cgi?pr=99517 From owner-freebsd-standards@FreeBSD.ORG Fri Aug 8 15:00:31 2008 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77D971065680 for ; Fri, 8 Aug 2008 15:00:31 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 040F38FC1E for ; Fri, 8 Aug 2008 15:00:30 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so509763nfh.33 for ; Fri, 08 Aug 2008 08:00:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=3LbnMryAYb0UsCIFCHfVvnvI9/B5Jqb7VCQ8RRv+ARM=; b=pFE2ntbCdZXylmymOs6n7J7cBxLD2naVG3JekQ0pug87oyEMEilJE7kEvKNNb20A24 Ymikg0n9KtJgz33pkhoCcNPpe0BZJWV98d/5MhPfq4kRgeczuKPoRAluTbuxpbBlwktV z6GrFCI6Rb9aqJ/gChGbPBivpgG0nh8CNvumI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=TCucdjx05z64hQN4KHZoh13JcD+0bAGJdlG8VgnyxUwvxbBvXGBCYFaMkM+6oDM4e8 NtMceaB+FUgAkIh2xcXkUZSJOd7C9ohLONvt4j15LGPLmyibjdcAWIKMhnbH/TxKP925 QpQPN5eoGTT9xBFWNTlwTnPCCicea6dhDT4xg= Received: by 10.103.131.18 with SMTP id i18mr3185344mun.116.1218206037760; Fri, 08 Aug 2008 07:33:57 -0700 (PDT) Received: by 10.103.169.13 with HTTP; Fri, 8 Aug 2008 07:33:57 -0700 (PDT) Message-ID: Date: Fri, 8 Aug 2008 11:33:57 -0300 From: "Carlos A. M. dos Santos" To: "Pieter de Goeje" In-Reply-To: <200808081009.56521.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> Cc: freebsd-hackers@freebsd.org, freebsd-standards@freebsd.org Subject: Re: read with timeout ?? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2008 15:00:31 -0000 On Fri, Aug 8, 2008 at 5:09 AM, Pieter de Goeje wrote: > On Friday 08 August 2008, Carlos A. M. dos Santos wrote: >> On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge > wrote: >> > On Thu, 7 Aug 2008, Chuck Robey wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> >> Hash: SHA1 >> >> >> >> I have my head lost in a code problem. I just hit a point where I need >> >> to do a >> >> read from an fd, but I need to associate it with a timeout, on the order >> >> of 1 >> >> second, something like that. I had the feeling that there's a function >> >> in FreeBSD's libc that makes that simple, but I forget the function >> >> name. If anyone can remember something like what I'm talking about, I >> >> sure would appreciate a function name. I can figure out how it works, >> >> if I could only >> >> dredge up that name. >> > >> > man 2 select >> >> If the fd is a socket then you can also use setsockopt(2) to set >> SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or >> recv(2) errors. The net effect is the same of using select but the >> syntax is simpler, IMO. > > I think poll(2) is also simpler than select for this purpose. BTW, the setsockopt(2) manual page stands that a send or receive timeout returns with the error EWOULDBLOCK but read(2) recv(2) send(2) and write(2) only list EAGAIN in their ERRORS section. This is harmless on BSD and Linux because EAGAIN and EWOULDBLOCK are the same, but may sound confusing for people porting from/to System V. On HP-UX, for instance, recv(2) lists both EAGAIN and EWOULDBLOCK. The setsockopt man page should be improved in order to explain standards conformance and porting issues. I volunteer to do it but the changes must be reviewed by a native English speaker. -- If you think things can't get worse it's probably only because you lack sufficient imagination. From owner-freebsd-standards@FreeBSD.ORG Fri Aug 8 20:57:43 2008 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 674F0106568F for ; Fri, 8 Aug 2008 20:57:43 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3FE1F8FC12 for ; Fri, 8 Aug 2008 20:57:43 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 775 invoked from network); 8 Aug 2008 20:31:03 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 8 Aug 2008 20:31:03 -0000 Message-ID: <489CACF9.3030309@telenix.org> Date: Fri, 08 Aug 2008 16:30:49 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: "Carlos A. M. dos Santos" References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> In-Reply-To: X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pieter de Goeje , freebsd-standards@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: read with timeout ?? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2008 20:57:43 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos A. M. dos Santos wrote: > On Fri, Aug 8, 2008 at 5:09 AM, Pieter de Goeje wrote: >> On Friday 08 August 2008, Carlos A. M. dos Santos wrote: >>> On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge >> wrote: >>>> On Thu, 7 Aug 2008, Chuck Robey wrote: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> I have my head lost in a code problem. I just hit a point where I need >>>>> to do a >>>>> read from an fd, but I need to associate it with a timeout, on the order >>>>> of 1 >>>>> second, something like that. I had the feeling that there's a function >>>>> in FreeBSD's libc that makes that simple, but I forget the function >>>>> name. If anyone can remember something like what I'm talking about, I >>>>> sure would appreciate a function name. I can figure out how it works, >>>>> if I could only >>>>> dredge up that name. >>>> man 2 select >>> If the fd is a socket then you can also use setsockopt(2) to set >>> SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or >>> recv(2) errors. The net effect is the same of using select but the >>> syntax is simpler, IMO. >> I think poll(2) is also simpler than select for this purpose. > > BTW, the setsockopt(2) manual page stands that a send or receive > timeout returns with the error EWOULDBLOCK but read(2) recv(2) send(2) > and write(2) only list EAGAIN in their ERRORS section. This is > harmless on BSD and Linux because EAGAIN and EWOULDBLOCK are the same, > but may sound confusing for people porting from/to System V. On HP-UX, > for instance, recv(2) lists both EAGAIN and EWOULDBLOCK. > > The setsockopt man page should be improved in order to explain > standards conformance and porting issues. I volunteer to do it but the > changes must be reviewed by a native English speaker. > Carlos, lets not go off on the socket trip for me... while I personally enjoy such a email, I have to admit my own needs fall more into a plain-jame serial line, nothing a socket-oriented thing could help me with. However, if you want to discuss this just fo the fun of it, oh please, by all means do carry on! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkicrPkACgkQz62J6PPcoOmJowCfWPt1jHY4Gx0kOAQedVATHYDd BGYAoJe6JYuskZZe85AA63sgRBG1VGF0 =dNTn -----END PGP SIGNATURE-----