From owner-freebsd-questions Tue Jan 28 02:59:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA05755 for questions-outgoing; Tue, 28 Jan 1997 02:59:22 -0800 (PST) Received: from quasi.bis.co.il (quasi.bis.co.il [192.115.114.40]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05750 for ; Tue, 28 Jan 1997 02:59:16 -0800 (PST) Received: from quasi.bis.co.il (localhost [127.0.0.1]) by quasi.bis.co.il (8.8.3/8.8.3) with SMTP id NAA00785; Tue, 28 Jan 1997 13:01:34 GMT Message-ID: <32EDF8AE.2781E494@bis.co.il> Date: Tue, 28 Jan 1997 13:01:34 +0000 From: Meir Dukhan Organization: Bis Software Systems Ltd X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6-RELEASE i386) MIME-Version: 1.0 To: questions@freebsd.org CC: mdukhan@quasi.bis.co.il Subject: Sys V IPC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Sys V ipc (at least the calls related to shared mem and messages queues) seems to _not_ be implemented as system calls. Indeed, ktrace/kdump wont records them as system calls (even if the manpage for shmat is in section 2 ;=) I experienced the following: - msgrcv() with IPC_NOWAIT return EWOULDBLOCK instead of ENOMSG (Linux and Sys V) - a process can have no more than 8 shared mem segments Is the above right ? Can one confirm/infirm ? Tia Meir