From owner-freebsd-questions Sat Dec 28 20:57:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA13961 for questions-outgoing; Sat, 28 Dec 1996 20:57:04 -0800 (PST) Received: from obie.softweyr.com (slc180.modem.xmission.com [204.228.136.180]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA13956 for ; Sat, 28 Dec 1996 20:57:00 -0800 (PST) Received: (from wes@localhost) by obie.softweyr.com (8.7.5/8.6.12) id WAA08836; Sat, 28 Dec 1996 22:00:03 -0700 (MST) Date: Sat, 28 Dec 1996 22:00:03 -0700 (MST) Message-Id: <199612290500.WAA08836@obie.softweyr.com> From: Wes Peters To: "Sean Batson (Sunbeach)" CC: questions@freebsd.org Subject: IPC API's In-Reply-To: References: Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sean Batson writes: > How do I go about coding for IPC applications? > Where online can I find the APIs to do such a > task. Under AIX I know the routines are msgsnd, > msgrcv and msgget. Got those same routines right here in FreeBSD. Be sure to include the following in your kernel configuration if you want them to work: options SYSVSHM options SYSVSEM options SYSVMSG Technically, you only need the first and the last, but why not get semaphores while you're at it? Has anyone out there ever wrapped a class around these so they're a little more usable? The SYSV IPC mechanisms are pretty powerful, but the semaphores and message queues have an *awful* interface. Hmmm... a nice little weekend (or two) project in C++ class construction. Any takers? (I.e. I don't want to do it myself; call me lazy.) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com