From owner-freebsd-stable Sat Jan 1 6:27: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157]) by hub.freebsd.org (Postfix) with ESMTP id E282F14FF4 for ; Sat, 1 Jan 2000 06:26:59 -0800 (PST) (envelope-from walterr@bellatlantic.net) Received: from bellatlantic.net (adsl-151-202-19-237.bellatlantic.net [151.202.19.237]) by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id JAA03228 for ; Sat, 1 Jan 2000 09:26:54 -0500 (EST) Message-ID: <386E0EB2.C4C45660@bellatlantic.net> Date: Sat, 01 Jan 2000 09:26:58 -0500 From: Tony Rentschler X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: sem_otime not updated? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm writing a program that uses a SysV semaphore, and it seems that the sem_otime field of the semid_ds struct is not updated after a call to semop. According to Steven's Unix Network Programming V2, the sem_otime field is set to zero when the semaphore is created, then is updated with the current time when semop is called. In /usr/sys/kern/sysv_sem.c on my 3.4 STABLE, I see that the sem_otime field is set to zero in the semget call, but is never referred to anyplace else. So, it looks like the source confirms my experiences. In a search of deja.com for sem_otime, I found a patch posted by Peter Jeremy on 6/4/99, but, as far as I can tell, that's for CURRENT. I've never worked with FreeBSD at this (low) level, but I wonder if the patch could be applied to STABLE? I'd prefer not to move to CURRENT, nor to apply the patch myself (because I'll forget about it a couple of months from now when I do a buildworld!). I'm open to suggestions on how best to proceed. Thanks, Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message