From owner-freebsd-standards@FreeBSD.ORG Mon Jul 26 11:07:12 2010 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 6FC0C1065675 for ; Mon, 26 Jul 2010 11:07:12 +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 643738FC08 for ; Mon, 26 Jul 2010 11:07:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6QB7Cpn080822 for ; Mon, 26 Jul 2010 11:07:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6QB7BOj080820 for freebsd-standards@FreeBSD.org; Mon, 26 Jul 2010 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Jul 2010 11:07:11 GMT Message-Id: <201007261107.o6QB7BOj080820@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, 26 Jul 2010 11:07:12 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/147210 standards xmmintrin.h and cstdlib conflicts with each other with p stand/145517 standards POSIX getline() missing o stand/145082 standards Patch against w(1) & uptime(1) to use 24H time by defa o stand/144231 standards bind/connect/sendto too strict about sockaddr length o stand/143358 standards [libm] nearbyint(3) raises spurious inexact exception o stand/142803 standards j0 Bessel function inaccurate near zeros of the functi s stand/141705 standards [libc] [request] libc lacks cexp (and friends) o stand/130067 standards Wrong numeric limits in system headers? o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/116826 standards [patch] sh support for POSIX character classes o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/96236 standards [patch] [posix] sed(1) incorrectly describes a functio o stand/96016 standards [headers] clock_getres et al should be in o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/82654 standards C99 long double math functions are missing o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( s stand/62858 standards malloc(0) not C99 compliant o stand/56476 standards [patch] cd9660 unicode support simple hack o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads p stand/41576 standards ln(1): replacing old dir-symlinks o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h s stand/24590 standards timezone function not compatible witn Single Unix Spec o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 43 problems total. From owner-freebsd-standards@FreeBSD.ORG Thu Jul 29 06:26:54 2010 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CADC1065672; Thu, 29 Jul 2010 06:26:54 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CF8308FC14; Thu, 29 Jul 2010 06:26:53 +0000 (UTC) Received: by iwn35 with SMTP id 35so326475iwn.13 for ; Wed, 28 Jul 2010 23:26:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=PEU5dOx2jKlgYHOSv1Mr0Zmf6a772ZRXY75on/0Ca/k=; b=XrIsrEoBzk5X2AmErw87EpDuTe40lxcEb0XpFl5eotJ/SQdpPD2LmnvZS/S3SvxUhu quyRr7QbR0zVx16WySH0Vkadnxj6mGNrKKYuwW1AA07lHtxYwEBVAvJZAbfI8jqDdbNT Kweja7rSC2jFwnP1IDBg6UebD1NDq+NQE2xuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=P1Ymru1q0qwHX0rTZbN3hNpqrf3q52txZwW/jxHJ+cKhSx4aTJGN+W4bcChlkYNHWj nuPZyCsfa0UAXIHjxlapurBH1DwnelSLobRMkJF6dzdhthJUB3LHo575gT07CBv6q+dp XaT+o9UHrkm4N5gpn3wlgO9i/Z3C5IzQ3BFd8= MIME-Version: 1.0 Received: by 10.231.184.68 with SMTP id cj4mr13562211ibb.93.1280384812889; Wed, 28 Jul 2010 23:26:52 -0700 (PDT) Received: by 10.231.169.18 with HTTP; Wed, 28 Jul 2010 23:26:52 -0700 (PDT) Date: Wed, 28 Jul 2010 23:26:52 -0700 Message-ID: From: Garrett Cooper To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: standards@freebsd.org Subject: Deterministic failure to meet sysconf(_SC_TIMER_MAX) for CLOCK_REALTIME 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: Thu, 29 Jul 2010 06:26:54 -0000 Hi, Running the following noted test [1], I always run into issues on the 29th iteration and EAGAIN: $ conformance/behavior/timers/1-1.run-test timer_create() did not return success for iteration 29: Resource temporarily unavailable $ conformance/behavior/timers/1-1.run-test timer_create() did not return success for iteration 29: Resource temporarily unavailable $ conformance/behavior/timers/1-1.run-test timer_create() did not return success for iteration 29: Resource temporarily unavailable $ conformance/behavior/timers/1-1.run-test timer_create() did not return success for iteration 29: Resource temporarily unavailable Interestingly enough, sysconf(_SC_TIMER_MAX) returns 54; this is the requirement that the test is attempting to validate (that at least _SC_TIMER_MAX timers can be created via timer_create). The timers kernel code is capped to 25 by default, by a preprocessor define in .../sys/sysctl.h: /sys/sys/sysctl.h:#define CTL_P1003_1B_TIMER_MAX 25 /* int */ Doesn't make sense why an additional 4 timers were created. Oh, and the sysctl reports something else entirely: p1003_1b.timers: 200112 p1003_1b.delaytimer_max: 2147483647 p1003_1b.timer_max: 32 So, what number is the source of truth and why don't they all match? Thanks! -Garrett PS I'm still running a CURRENT kernel based off of r206173... [1] http://ltp.git.sourceforge.net/git/gitweb.cgi?p=ltp/ltp-dev.git;a=blob;f=testcases/open_posix_testsuite/conformance/behavior/timers/1-1.c;h=ac043b0913e93f8db93cc74e249316f5ff82bdc8;hb=HEAD From owner-freebsd-standards@FreeBSD.ORG Thu Jul 29 06:47:04 2010 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2C7B106567B for ; Thu, 29 Jul 2010 06:47:04 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9EED78FC16 for ; Thu, 29 Jul 2010 06:47:04 +0000 (UTC) Received: by iwn35 with SMTP id 35so18512iwn.13 for ; Wed, 28 Jul 2010 23:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=PfbrF/DLX9A744swQLmQnRVov5qiVzIoq6BsbpuAUJg=; b=lExFND2Ak8gEyonrudVGXKnDWNWk31qZkXo/CBSN0n3a5OKN8+plmyoUL3bDDKwUcx Mf7fimwVnWeWd0QNEe9l+gXTHcTMfrzB/shDVgZX+1kHvST6piLy3k+WDzFjxOQngUHD rdsTe3+GsbEPFOgnDKUZzGWj3BcyyllzncNX8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=Q1BvQWIR85fm3mMdZpRpFsSiTk5/NebepRBJY0UdeZe5IJc4g9x3ogoyR13dyYoSiS GVxkxftgyt24+3J/DhfrAJZYW1+OkxDy1a5ZvdsX/fD6tpIUZnsjiJB22eJ7LhDMobbr qC8JCJL2y718pEW5624YhAF7Onffye4/qSCrI= MIME-Version: 1.0 Received: by 10.231.32.69 with SMTP id b5mr13331401ibd.153.1280386023537; Wed, 28 Jul 2010 23:47:03 -0700 (PDT) Received: by 10.231.169.18 with HTTP; Wed, 28 Jul 2010 23:47:03 -0700 (PDT) Date: Wed, 28 Jul 2010 23:47:03 -0700 Message-ID: From: Garrett Cooper To: alc@freebsd.org, Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Cc: standards@freebsd.org Subject: POSIX compliance issue with mmap(2) 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: Thu, 29 Jul 2010 06:47:04 -0000 According to the page noted below [1], mmap(2) should fail if the value isn't page-aligned: [EINVAL] The addr argument (if MAP_FIXED was specified) or off is not a multiple of the page size as returned by sysconf(), or is considered invalid by the implementation. The current code in vm/vm_mmap.c only applies the check if MAP_FIXED is specified in flags: /* * Check for illegal addresses. Watch out for address wrap... Note * that VM_*_ADDRESS are not constants due to casts (argh). */ if (flags & MAP_FIXED) { /* * The specified address must have the same remainder * as the file offset taken modulo PAGE_SIZE, so it * should be aligned after adjustment by pageoff. */ addr -= pageoff; if (addr & PAGE_MASK) return (EINVAL); Our manpage states this requirement, but doesn't conform to the POSIX requirements. I verified this claim with the failing test [2] by changing MAP_SHARED to MAP_FIXED. The former case failed, while the latter case passed. Thoughts? -Garrett [1] http://www.opengroup.org/onlinepubs/000095399/functions/mmap.html [2] http://ltp.git.sourceforge.net/git/gitweb.cgi?p=ltp/ltp-dev.git;a=blob;f=testcases/open_posix_testsuite/conformance/interfaces/mmap/11-1.c;h=ed184a17591f0dbb5611ab70218a763a8a66b2df;hb=HEAD From owner-freebsd-standards@FreeBSD.ORG Thu Jul 29 15:55:02 2010 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BAA71065674; Thu, 29 Jul 2010 15:55:02 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.freebsd.org (Postfix) with ESMTP id B4E688FC1D; Thu, 29 Jul 2010 15:55:01 +0000 (UTC) Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1]) by khavrinen.csail.mit.edu (8.14.4/8.14.4) with ESMTP id o6TFKehk014640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA); Thu, 29 Jul 2010 11:20:40 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.14.4/8.14.4/Submit) id o6TFKetI014637; Thu, 29 Jul 2010 11:20:40 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19537.40008.156802.846800@khavrinen.csail.mit.edu> Date: Thu, 29 Jul 2010 11:20:40 -0400 From: Garrett Wollman To: Garrett Cooper In-Reply-To: References: X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (khavrinen.csail.mit.edu [127.0.0.1]); Thu, 29 Jul 2010 11:20:40 -0400 (EDT) Cc: alc@freebsd.org, standards@freebsd.org Subject: POSIX compliance issue with mmap(2) 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: Thu, 29 Jul 2010 15:55:02 -0000 < said: > According to the page noted below [1], mmap(2) should fail if the > value isn't page-aligned: > [EINVAL] > The addr argument (if MAP_FIXED was specified) or off is not a > multiple of the page size as returned by sysconf(), or is considered > invalid by the implementation. This may be a bug in the standard (since this is a "shall fail" condition, and there's no reason it has to fail if the application didn't specify MAP_FIXED). -GAWollman From owner-freebsd-standards@FreeBSD.ORG Thu Jul 29 16:39:00 2010 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91541106564A; Thu, 29 Jul 2010 16:39:00 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 38D178FC1B; Thu, 29 Jul 2010 16:38:59 +0000 (UTC) Received: by gwj23 with SMTP id 23so247790gwj.13 for ; Thu, 29 Jul 2010 09:38:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=84bY5VOkL/baAUBsgTG5teiS+j+UEMfyd0Wj12HnMbQ=; b=Et6Fle8G1EBsXMyGlMZrCBDBob2xsTHOhjIqXqpTSvHSOLwiGMrTmT/yAC2oz9FvB4 neUryNqsJbbqbhSzHfzeGyQ/DmdfFuSBwRtXfHoyXx1dwUTC5RljTq33ACjf9jkQbBQ+ fWlYNRX/umzYwGRs32Y6yaimTgafjFg4Y8TxM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KQZCexAgbyHpuuTZXzsZuCbAjRfbcrlB2EobnFtfpnWvp5a6fgyuzodX81UOldI1qf rtNtySw1HgVCJLxBr8i/EIuQd3lsdN2wOucRHku6v7m8xl0hJC7R0kPyUBXkXIlNVsfF Fuzr3/QtR31h3ejT3FEXqTDiH6UA8O/ky/gSk= MIME-Version: 1.0 Received: by 10.101.143.38 with SMTP id v38mr464734ann.56.1280421539280; Thu, 29 Jul 2010 09:38:59 -0700 (PDT) Received: by 10.231.169.18 with HTTP; Thu, 29 Jul 2010 09:38:59 -0700 (PDT) In-Reply-To: <19537.40008.156802.846800@khavrinen.csail.mit.edu> References: <19537.40008.156802.846800@khavrinen.csail.mit.edu> Date: Thu, 29 Jul 2010 09:38:59 -0700 Message-ID: From: Garrett Cooper To: Garrett Wollman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: alc@freebsd.org, standards@freebsd.org Subject: Re: POSIX compliance issue with mmap(2) 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: Thu, 29 Jul 2010 16:39:00 -0000 On Thu, Jul 29, 2010 at 8:20 AM, Garrett Wollman wr= ote: > <= said: > >> =A0 =A0 According to the page noted below [1], mmap(2) should fail if th= e >> value isn't page-aligned: > >> [EINVAL] >> =A0 =A0 The addr argument (if MAP_FIXED was specified) or off is not a >> multiple of the page size as returned by sysconf(), or is considered >> invalid by the implementation. > > This may be a bug in the standard (since this is a "shall fail" > condition, and there's no reason it has to fail if the application > didn't specify MAP_FIXED). There are a number of opengroup manpages I've seen use the `shall fail' tort in the ERRORs sections -- some being connect(2), open(2), etc. I'll see if I can get clarification on whether or not there is any wiggle room if it states "shall fail if". Thanks, -Garrett From owner-freebsd-standards@FreeBSD.ORG Thu Jul 29 17:01:04 2010 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3E19106567C for ; Thu, 29 Jul 2010 17:01:04 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.freebsd.org (Postfix) with ESMTP id 817538FC0C for ; Thu, 29 Jul 2010 17:01:04 +0000 (UTC) Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1]) by khavrinen.csail.mit.edu (8.14.4/8.14.4) with ESMTP id o6TH13Ma016851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA); Thu, 29 Jul 2010 13:01:03 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.14.4/8.14.4/Submit) id o6TH139L016848; Thu, 29 Jul 2010 13:01:03 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19537.46031.343891.856928@khavrinen.csail.mit.edu> Date: Thu, 29 Jul 2010 13:01:03 -0400 From: Garrett Wollman To: Garrett Cooper In-Reply-To: References: <19537.40008.156802.846800@khavrinen.csail.mit.edu> X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (khavrinen.csail.mit.edu [127.0.0.1]); Thu, 29 Jul 2010 13:01:03 -0400 (EDT) Cc: standards@freebsd.org Subject: Re: POSIX compliance issue with mmap(2) 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: Thu, 29 Jul 2010 17:01:04 -0000 < said: > There are a number of opengroup manpages I've seen use the `shall > fail' tort in the ERRORs sections -- some being connect(2), open(2), > etc. I'll see if I can get clarification on whether or not there is > any wiggle room if it states "shall fail if". "Shall" is a mandatory requirement; if it were optional, it would say "may" instead. (A conformance test has to include at least one test for every instance of the word "shall" in the standard.) If there are other examples of "shall fail" errors that you think should be "may fail" errors instead, you should bring them up on the Austin Group mailing-list. -GAWollman From owner-freebsd-standards@FreeBSD.ORG Thu Jul 29 22:43:28 2010 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 4FA2C1065674; Thu, 29 Jul 2010 22:43:28 +0000 (UTC) (envelope-from jilles@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 251588FC15; Thu, 29 Jul 2010 22:43:28 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6TMhSCC007551; Thu, 29 Jul 2010 22:43:28 GMT (envelope-from jilles@freefall.freebsd.org) Received: (from jilles@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6TMhSnW007547; Thu, 29 Jul 2010 22:43:28 GMT (envelope-from jilles) Date: Thu, 29 Jul 2010 22:43:28 GMT Message-Id: <201007292243.o6TMhSnW007547@freefall.freebsd.org> To: jilles@FreeBSD.org, freebsd-standards@FreeBSD.org, freebsd-bugs@FreeBSD.org From: jilles@FreeBSD.org Cc: Subject: Re: bin/145082: Patch against w(1) & uptime(1) to use 24H time by default. 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: Thu, 29 Jul 2010 22:43:28 -0000 Synopsis: Patch against w(1) & uptime(1) to use 24H time by default. Responsible-Changed-From-To: freebsd-standards->freebsd-bugs Responsible-Changed-By: jilles Responsible-Changed-When: Thu Jul 29 22:41:10 UTC 2010 Responsible-Changed-Why: This is not a standards compliance issue as w and uptime are not in POSIX. Regarding the patch, how does a user select 12h output? I tried LANG=en_US.ISO8859-1 w and it still gave 24h. http://www.freebsd.org/cgi/query-pr.cgi?pr=145082