Article View: comp.sys.sun
Article #11308problem with shared memory
From: Tod Pike
Date: Mon, 06 Mar 1989 03:33
Date: Mon, 06 Mar 1989 03:33
20 lines
1350 bytes
1350 bytes
I recently had a problem submitted to me that I thought the net would be able to help with. A group here has a system that uses shared memory extensively. This application works fine on a Microvax, but they were having problems with it on Suns (3/60's). The first process would create a shared memory segment, and attach to it OK, but a second process could not attach to the segment, getting EINVAL. I "fixed" the problem by replacing the more or less generic kernel on their 3/60's with a kernel config'd just for their machine. Both configs had the "options IPCSHMEM", "options IPCSEMAPHORE" and "options IPCMESSAGE" set. I am mystified as to why the specific kernel worked and the generic kernel did not. Any ideas? Much Thanks, Tod Pike tgp@sei.cmu.edu Software Engineering Institute Carnegie Mellon University Pittsburgh, PA. 15213
Technical Details
Message-ID:
<8902232038.AA12322@dj.sei.cmu.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-requestShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request From: tgp@sei.cmu.edu (Tod Pike) Newsgroups: comp.sys.sun Subject: problem with shared memory Keywords: SunOS Message-ID: <8902232038.AA12322@dj.sei.cmu.edu> Date: 6 Mar 89 03:33:32 GMT Sender: usenet@rice.edu Organization: Sun-Spots Lines: 20 Approved: Sun-Spots@rice.edu Original-Date: Thu, 23 Feb 89 15:38:55 EST X-Sun-Spots-Digest: Volume 7, Issue 182, message 16 of 17