Loadable driver nipc breaks ipcs(1) on UNIX pc.

Lenny Tropiano lenny at icus.UUCP
Mon Jun 6 14:25:10 AEST 1988


I was having some problems with interprocess communications on the UNIX pc
just recently.  I was getting weird results like EMT trap - core dumps on
programs that I know run.   I remember something in the 3.51 books saying
their was a non-certified version of the interprocess communications driver
called "nipc", so I proceeded to unbind and deallocate the nipc driver
(I used the "Setup loadable device drivers" from the User Agent) and
then loaded "nipc".  All seemed to go well.  I rebooted, although I shouldn't
have to since they are dynamically allocated...

I logged in and did a ipcs to see what was in my "message queue" and
my "shared memory" blocks were set up, and I got:

$ ipcs
IPC status from /dev/kmem as of Mon Jun  6 00:24:33 1988
Message Queue facility not in system.
Shared Memory facility not in system.
Semaphore facility not in system.

What do you mean they are not a facility in the system.  The programs
are running just fine (or so they seem).  What should I do?

-Lenny
-- 
US MAIL  : Lenny Tropiano, ICUS Computer Group        IIIII  CCC U   U  SSS
           PO Box 1                                     I   C    U   U S
           Islip Terrace, New York  11752               I   C    U   U  SS 
PHONE    : (516) 968-8576 [H] (516) 582-5525 [W]        I   C    U   U    S
TELEX    : 154232428 [ICUS]                           IIIII  CCC  UUU  SSS 
AT&T MAIL: ...attmail!icus!lenny  
UUCP     : ...{mtune, ihnp4, boulder, talcott, sbcs, bc-cis}!icus!lenny 



More information about the Unix-pc.general mailing list