Insufficient Resource Error on msgsnd Call

Charles Noren noren at dinl.uucp
Fri May 26 00:13:41 AEST 1989


In article <8340 at june.cs.washington.edu> ka at june.cs.washington.edu (Kenneth Almquist) writes:
]>    +--------+                +--------+                +--------+
]>    |        |      +-----+   |        |      +-----+   |        |
]>    | Proc A |---->>| Q 1 |-->| Proc B |---->>| Q 2 |-->| Proc C |
]>    |        |      +-----+   |        |      +-----+   |        |
]>    +--------+                +--------+                +--------+
]
]On the other hand, you write:
]
]> Queue 2 looks empty because Process C is blocking on it (using
]> msgsnd with IPC_WAIT) ...
]> reading Queue 2 several times breaks the log jam and the system runs
           ^^^^^^^
]> for a while ...
]
]If you can read messages off of queue 2 while process C is blocked on a
]read, that indicates a kernel bug.  Probably the msgsnd system call is
]failing to call wakeup for some reason.
]				Kenneth Almquist

Oops, I meant to say Queue 1.  Several have caught me on this one.
I'm glad to see all of the good responses in spite of mis-stating
some of the information.

-- 
Chuck Noren
NET:     ncar!dinl!noren
US-MAIL: Martin Marietta I&CS, MS XL8058, P.O. Box 1260,
         Denver, CO 80201-1260
Phone:   (303) 971-7930



More information about the Comp.unix.questions mailing list