From owner-freebsd-current Wed Jul 15 15:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26750 for freebsd-current-outgoing; Wed, 15 Jul 1998 15:28:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phobos.muc.de (phobos.muc.de [193.174.4.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26742 for ; Wed, 15 Jul 1998 15:28:15 -0700 (PDT) (envelope-from ras@phobos.muc.de) Received: (from ras@localhost) by phobos.muc.de (8.8.8/8.8.5) id AAA08114; Thu, 16 Jul 1998 00:25:23 +0200 (MET DST) Date: Thu, 16 Jul 1998 00:25:22 +0200 (MET DST) From: Rudolf Schreiner To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Where is F_LOCK defined? In-Reply-To: <19980715140148.A10804@top.worldcontrol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Jul 1998 brian@worldcontrol.com wrote: > Where is F_LOCK or F_ULOCK defined? That's SYSV style record locking, check lockf(3C) e.g. on Solaris 2.6. Lockf is not supported by BSD, I had the same problem when I ported SESAME to FreeBSD (2.2.6). I used the lockf function from glibc, it seems to work. Rudi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message