From owner-freebsd-standards@FreeBSD.ORG Tue Jun 17 23:29:14 2003 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 265C737B401 for ; Tue, 17 Jun 2003 23:29:14 -0700 (PDT) Received: from web13408.mail.yahoo.com (web13408.mail.yahoo.com [216.136.175.66]) by mx1.FreeBSD.org (Postfix) with SMTP id BA82543FAF for ; Tue, 17 Jun 2003 23:29:13 -0700 (PDT) (envelope-from giffunip@yahoo.com) Message-ID: <20030618062913.65840.qmail@web13408.mail.yahoo.com> Received: from [200.91.194.88] by web13408.mail.yahoo.com via HTTP; Wed, 18 Jun 2003 08:29:13 CEST Date: Wed, 18 Jun 2003 08:29:13 +0200 (CEST) From: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" To: freebsd-standards@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: sigpause not POSIX compliant? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 06:29:14 -0000 Just FYI; I was curious about the (outdated) notes of the FreeBSD glibc porting attempt: http://www.haible.de/bruno/gnu-freebsd/glibc-port and I caught this: "Clean up sigpause implementation (not POSIX compliant)." sigpause appears as "obsoleted by sigsuspend" on our manpages but it does apear on the UNIX API list: http://www.unix-systems.org/version3/apis/t_8.html no idea if this info is useful at all, but well if this list is not interested, nobody is :). cheers, Pedro. ______________________________________________________________________ Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro Anti-spam http://it.yahoo.com/mail_it/foot/?http://it.mail.yahoo.com/ From owner-freebsd-standards@FreeBSD.ORG Wed Jun 18 11:38:29 2003 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DFE337B401 for ; Wed, 18 Jun 2003 11:38:29 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE34C43FAF for ; Wed, 18 Jun 2003 11:38:28 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h5IIcRjp042709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 18 Jun 2003 14:38:28 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id h5IIcRQp042706; Wed, 18 Jun 2003 14:38:27 -0400 (EDT) (envelope-from wollman) Date: Wed, 18 Jun 2003 14:38:27 -0400 (EDT) From: Garrett Wollman Message-Id: <200306181838.h5IIcRQp042706@khavrinen.lcs.mit.edu> To: "=?iso-8859-1?q?Pedro=20F.=20Giffuni?=" In-Reply-To: <20030618062913.65840.qmail@web13408.mail.yahoo.com> References: <20030618062913.65840.qmail@web13408.mail.yahoo.com> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: freebsd-standards@freebsd.org Subject: sigpause not POSIX compliant? X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 18:38:29 -0000 < said: > sigpause appears as "obsoleted by sigsuspend" on our manpages > but it does apear on the UNIX API list: > http://www.unix-systems.org/version3/apis/t_8.html It actually is an obsolete interface, it's just not marked as such. sigsuspend() was introduced with the POSIX signal model and is a superior interface. Unfortunately, the merger between POSIX and SUS resulted in some of the old (and in some cases broken) SUS interfaces being introduced into POSIX for the first time (having been rightly rejected by SSWG in previous rounds). Our sigpause() does something completely different (hardly unsurprising), and expects an old 4.2-style signal mask rather than a single signal number. -GAWollman From owner-freebsd-standards@FreeBSD.ORG Fri Jun 20 07:21:44 2003 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4E2B37B401; Fri, 20 Jun 2003 07:21:44 -0700 (PDT) Received: from atlas.informatik.rwth-aachen.de (atlas.Informatik.RWTH-Aachen.DE [137.226.194.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08A8B43FA3; Fri, 20 Jun 2003 07:21:43 -0700 (PDT) (envelope-from stolz@i2.informatik.rwth-aachen.de) Received: from menelaos.informatik.rwth-aachen.de (menelaos.Informatik.RWTH-Aachen.DE [137.226.194.73]) 8.11.1-0.5) with ESMTP id h5KELgK20857; Fri, 20 Jun 2003 16:21:42 +0200 Received: (from stolz@localhost)h5KELfUh011622; Fri, 20 Jun 2003 16:21:42 +0200 (CEST) (envelope-from stolz) Date: Fri, 20 Jun 2003 16:21:42 +0200 (CEST) Message-Id: <200306201421.h5KELfUh011622@menelaos.informatik.rwth-aachen.de> To: FreeBSD-gnats-submit@freebsd.org From: Volker Stolz X-send-pr-version: 3.113 X-GNATS-Notify: cc: standards@freebsd.org Subject: interval timers not cleared in fork() X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Volker Stolz List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2003 14:21:45 -0000 >Submitter-Id: current-users >Originator: Volker Stolz >Organization: Lehrstuhl für Informatik II >Confidential: no >Synopsis: interval timers not cleared in fork() >Severity: serious >Priority: low >Category: standards >Class: sw-bug >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD menelaos.informatik.rwth-aachen.de 4.8-STABLE FreeBSD 4.8-STABLE #4: Tue Apr 29 11:28:13 CEST 2003 root@menelaos.informatik.rwth-aachen.de:/usr/obj/usr/src/sys/MENELAOS i386 >Description: The FreeBSD man page says on calling fork(): "All interval timers are cleared; see setitimer(2)." SUSv2 says that on invoking fork(): - If the Timers option is supported, per-process timers created by the parent are not inherited by the child process. However, a quick test reveals that only the REAL timer is stopped, PROF and VIRTUAL keep running. >How-To-Repeat: Sample program which sets the timers, forks and checks if timers are still enabled in the child at: http://www.foldr.org/~stolz/timer.c virtual set: interval=1 500 value=1 500 REAL get: interval=0 0 value=0 0 PROF get: interval=1 500 value=1 500 VIRTUAL get: interval=1 500 value=1 500 >Fix: From owner-freebsd-standards@FreeBSD.ORG Fri Jun 20 07:30:13 2003 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56B5337B401 for ; Fri, 20 Jun 2003 07:30:13 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B4CA43FDD for ; Fri, 20 Jun 2003 07:30:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5KEUCUp022054 for ; Fri, 20 Jun 2003 07:30:12 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5KEUCFt022053; Fri, 20 Jun 2003 07:30:12 -0700 (PDT) Resent-Date: Fri, 20 Jun 2003 07:30:12 -0700 (PDT) Resent-Message-Id: <200306201430.h5KEUCFt022053@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-standards@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Volker Stolz Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4E2B37B401; Fri, 20 Jun 2003 07:21:44 -0700 (PDT) Received: from atlas.informatik.rwth-aachen.de (atlas.Informatik.RWTH-Aachen.DE [137.226.194.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08A8B43FA3; Fri, 20 Jun 2003 07:21:43 -0700 (PDT) (envelope-from stolz@i2.informatik.rwth-aachen.de) Received: from menelaos.informatik.rwth-aachen.de (menelaos.Informatik.RWTH-Aachen.DE [137.226.194.73]) 8.11.1-0.5) with ESMTP id h5KELgK20857; Fri, 20 Jun 2003 16:21:42 +0200 Received: (from stolz@localhost)h5KELfUh011622; Fri, 20 Jun 2003 16:21:42 +0200 (CEST) (envelope-from stolz) Message-Id: <200306201421.h5KELfUh011622@menelaos.informatik.rwth-aachen.de> Date: Fri, 20 Jun 2003 16:21:42 +0200 (CEST) From: Volker Stolz To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 cc: standards@FreeBSD.org Subject: standards/53554: interval timers not cleared in fork() X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Volker Stolz List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2003 14:30:13 -0000 >Number: 53554 >Category: standards >Synopsis: interval timers not cleared in fork() >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 20 07:30:11 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Volker Stolz >Release: FreeBSD 4.8-STABLE i386 >Organization: Lehrstuhl für Informatik II >Environment: System: FreeBSD menelaos.informatik.rwth-aachen.de 4.8-STABLE FreeBSD 4.8-STABLE #4: Tue Apr 29 11:28:13 CEST 2003 root@menelaos.informatik.rwth-aachen.de:/usr/obj/usr/src/sys/MENELAOS i386 >Description: The FreeBSD man page says on calling fork(): "All interval timers are cleared; see setitimer(2)." SUSv2 says that on invoking fork(): - If the Timers option is supported, per-process timers created by the parent are not inherited by the child process. However, a quick test reveals that only the REAL timer is stopped, PROF and VIRTUAL keep running. >How-To-Repeat: Sample program which sets the timers, forks and checks if timers are still enabled in the child at: http://www.foldr.org/~stolz/timer.c virtual set: interval=1 500 value=1 500 REAL get: interval=0 0 value=0 0 PROF get: interval=1 500 value=1 500 VIRTUAL get: interval=1 500 value=1 500 >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-standards@FreeBSD.ORG Sat Jun 21 08:20:14 2003 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B252B37B401 for ; Sat, 21 Jun 2003 08:20:14 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42CF243F75 for ; Sat, 21 Jun 2003 08:20:14 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5LFKDUp065545 for ; Sat, 21 Jun 2003 08:20:13 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5LFKDLm065544; Sat, 21 Jun 2003 08:20:13 -0700 (PDT) Date: Sat, 21 Jun 2003 08:20:13 -0700 (PDT) Message-Id: <200306211520.h5LFKDLm065544@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Bruce M Simpson Subject: Re: docs/20528: sysconf(3) manpage doesn't mention posix.1b options X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bruce M Simpson List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2003 15:20:15 -0000 The following reply was made to PR docs/20528; it has been noted by GNATS. From: Bruce M Simpson To: freebsd-gnats-submit@FreeBSD.org Cc: mkb@altair.mayn.de, nik@freebsd.org, tjr@freebsd.org Subject: Re: docs/20528: sysconf(3) manpage doesn't mention posix.1b options Date: Sat, 21 Jun 2003 16:16:57 +0100 --BXr400anF0jyguTS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Here's a patch that adds the __POSIX_VISIBLE >= 199309 sysconf variables to our sysconf(3) manpage. BMS --BXr400anF0jyguTS Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sysconf.patch" Generated by diffcoll on Sat 21 Jun 2003 16:13:31 BST diff -uN src/lib/libc/gen/sysconf.3.orig src/lib/libc/gen/sysconf.3 --- /usr/src/lib/libc/gen/sysconf.3.orig Sat Jun 21 15:41:57 2003 +++ /usr/src/lib/libc/gen/sysconf.3 Sat Jun 21 16:13:21 2003 @@ -164,6 +164,84 @@ .It Li _SC_2_UPE Return 1 if the system supports the User Portability Utilities Option, otherwise \-1. +.It Li _SC_ASYNCHRONOUS_IO +Return 1 if the system supports Asynchronous I/O facilities as described in +.St -p1003.1 , +otherwise \-1. +.It Li _SC_MAPPED_FILES +Return 1 if the system supports memory mapped files, otherwise \-1. +.It Li _SC_MEMLOCK +Return 1 if the system supports process memory locking, otherwise \-1. +.It Li _SC_MEMLOCK_RANGE +Return 1 if the system supports range memory locking, otherwise \-1. +.It Li _SC_MEMORY_PROTECTION +Return 1 if the system supports memory protection, otherwise \-1. +.It Li _SC_MESSAGE_PASSING +Return 1 if the system supports POSIX message queues, otherwise \-1. +.It Li _SC_PRIORITIZED_IO +Return 1 if the system supports POSIX prioritized I/O, otherwise \-1. +.It Li _SC_PRIORITY_SCHEDULING +Return 1 if the system supports POSIX priority scheduling, otherwise \-1. +.It Li _SC_REALTIME_SIGNALS +Return 1 if the system supports POSIX realtime signals, otherwise \-1. +.It Li _SC_SEMAPHORES +Return 1 if the system supports POSIX semaphores, otherwise \-1. +.It Li _SC_FSYNC +Return 1 if the system supports file synchronization, otherwise \-1. +.It Li _SC_RAW_SOCKETS +Return 1 if the system supports +.Dv SOCK_RAW +style raw sockets, otherwise \-1. +.It Li _SC_SHARED_MEMORY_OBJECTS +Return 1 if the system supports POSIX shared memory objects, otherwise \-1. +.It Li _SC_SYNCHRONIZED_IO +Return 1 if the system supports POSIX synchronized I/O, otherwise \-1. +.It Li _SC_TIMERS +Return 1 if the system supports POSIX timers, otherwise \-1. +.It Li _SC_IPV6 +Return 1 if the system supports Internet Protocol version 6, otherwise \-1. +.It Li _SC_AIO_LISTIO_MAX +The maximum number of POSIX asynchronous I/O operations supported. +.It Li _SC_AIO_MAX +The maximum number of outstanding asynchronous I/O operations supported. +.It Li _SC_AIO_PRIO_DELTA_MAX +The maximum amount by which a process can decrease its asynchronous +I/O priority level from its own scheduling priority. +.It Li _SC_DELAYTIMER_MAX +The maximum number of timer expiration overruns permitted for each process. +.It Li _SC_MQ_OPEN_MAX +The maximum number of open POSIX message queues which a process may hold. +.It Li _SC_PAGESIZE +The system memory page size. +.It Li _SC_PAGE_SIZE +This is a synonym for +.Dv _SC_PAGESIZE . +.It Li _SC_RTSIG_MAX +The number of the highest POSIX realtime signal supported. +.It Li _SC_SEM_NSEMS_MAX +The maximum number of POSIX semaphores that a process may have. +.It Li _SC_SEM_VALUE_MAX +The maximum value that a POSIX semaphore may have. +.It Li _SC_SIGQUEUE_MAX +The maximum number of POSIX queued signals that a process may send and +have pending at receiver(s) at any given time. +.It Li _SC_TIMER_MAX +The maximum number of POSIX timers that a process may request. +.It Li _SC_NPROCESSORS_ONLN +The number of processors that are online and running in the system. +.It Li _SC_NPROCESSORS_CONF +The number of processors that are configured, but not +necessarily running, in the system. +.It Li _SC_IOV_MAX +The maximum number of iovec structures that one process may use with the +.Fn readv +and +.Fn writev +functions. +.It Li _SC_ATEXIT_MAX +The maximum number of functions that a process may register with the +.Fn atexit +function. .El .Sh RETURN VALUES If the call to --BXr400anF0jyguTS-- From owner-freebsd-standards@FreeBSD.ORG Sat Jun 21 09:34:47 2003 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3158237B401; Sat, 21 Jun 2003 09:34:47 -0700 (PDT) Received: from mail.tepkom.ru (mail.tepkom.ru [195.9.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F76043F85; Sat, 21 Jun 2003 09:34:44 -0700 (PDT) (envelope-from wart@mojo.tepkom.ru) Received: from localhost (localhost [127.0.0.1]) by mail.tepkom.ru (Postfix) with SMTP id C2AF197245; Sat, 21 Jun 2003 20:41:35 +0400 (MSD) Received: from mojo.tepkom.ru (mojo.tepkom.ru [195.9.10.30]) by mail.tepkom.ru (Postfix) with ESMTP id AA90A9722E; Sat, 21 Jun 2003 20:41:35 +0400 (MSD) Received: from wart by mojo.tepkom.ru with local (Exim 3.36 #1 (Debian)) id 19TlKD-0004zf-00; Sat, 21 Jun 2003 20:34:49 +0400 Date: Sat, 21 Jun 2003 20:34:49 +0400 From: Wartan Hachaturow To: Volker Stolz Message-ID: <20030621163449.GA19155@mojo.tepkom.ru> References: <200306201421.h5KELfUh011622@menelaos.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200306201421.h5KELfUh011622@menelaos.informatik.rwth-aachen.de> User-Agent: Mutt/1.4i Sender: Wartan Hachaturow cc: standards@freebsd.org cc: FreeBSD-gnats-submit@freebsd.org Subject: standards/53554 fix for review (Re: interval timers not cleared in fork()) X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2003 16:34:47 -0000 On Fri, Jun 20, 2003 at 04:21:42PM +0200, Volker Stolz wrote: > SUSv2 says that on invoking fork(): > - If the Timers option is supported, per-process timers created by the > parent are not inherited by the child process. SUSv3 requires this as well. This is a quick fix (for 5.1, it's also affected): --- ./resourcevar.h.orig Sat Jun 21 16:22:10 2003 +++ ./resourcevar.h Sat Jun 21 16:25:33 2003 @@ -52,11 +52,10 @@ #define pstat_startzero p_ru struct rusage p_ru; /* stats for this proc */ struct rusage p_cru; /* sum of stats for reaped children */ -#define pstat_endzero pstat_startcopy - -#define pstat_startcopy p_timer struct itimerval p_timer[3]; /* virtual-time timers */ +#define pstat_endzero pstat_startcopy +#define pstat_startcopy p_prof struct uprof { /* profile arguments */ caddr_t pr_base; /* buffer base */ u_long pr_size; /* buffer size */ -- Regards, Wartan. "Computers are not intelligent. They only think they are." From owner-freebsd-standards@FreeBSD.ORG Sat Jun 21 09:40:08 2003 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BD9B37B401 for ; Sat, 21 Jun 2003 09:40:08 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C238143FBD for ; Sat, 21 Jun 2003 09:40:07 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h5LGe7Up071884 for ; Sat, 21 Jun 2003 09:40:07 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h5LGe69X071883; Sat, 21 Jun 2003 09:40:06 -0700 (PDT) Date: Sat, 21 Jun 2003 09:40:06 -0700 (PDT) Message-Id: <200306211640.h5LGe69X071883@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Wartan Hachaturow Subject: standards/53554 fix for review (Re: interval timers not cleared in fork()) X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Wartan Hachaturow List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2003 16:40:08 -0000 The following reply was made to PR standards/53554; it has been noted by GNATS. From: Wartan Hachaturow To: Volker Stolz Cc: FreeBSD-gnats-submit@freebsd.org, standards@freebsd.org Subject: standards/53554 fix for review (Re: interval timers not cleared in fork()) Date: Sat, 21 Jun 2003 20:34:49 +0400 On Fri, Jun 20, 2003 at 04:21:42PM +0200, Volker Stolz wrote: > SUSv2 says that on invoking fork(): > - If the Timers option is supported, per-process timers created by the > parent are not inherited by the child process. SUSv3 requires this as well. This is a quick fix (for 5.1, it's also affected): --- ./resourcevar.h.orig Sat Jun 21 16:22:10 2003 +++ ./resourcevar.h Sat Jun 21 16:25:33 2003 @@ -52,11 +52,10 @@ #define pstat_startzero p_ru struct rusage p_ru; /* stats for this proc */ struct rusage p_cru; /* sum of stats for reaped children */ -#define pstat_endzero pstat_startcopy - -#define pstat_startcopy p_timer struct itimerval p_timer[3]; /* virtual-time timers */ +#define pstat_endzero pstat_startcopy +#define pstat_startcopy p_prof struct uprof { /* profile arguments */ caddr_t pr_base; /* buffer base */ u_long pr_size; /* buffer size */ -- Regards, Wartan. "Computers are not intelligent. They only think they are."