Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B7160B7.7040002@ece.gatech.edu>
Date: Wed, 08 Aug 2001 11:54:31 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Kiran C <kiranc AT tataelxsi DOT co DOT in>
CC: cygwin AT cygwin DOT com
Subject: Re: Using CygIPC
References: <026301c11fda$3c9a20b0$5328010a AT tataelxsi DOT co DOT in>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Kiran C wrote:

> Hi,
>     When I create a message queue using msgget and the don't close it.
> Some times later when I use the msget  function it gets stuck.


That's odd.


>    Is it that I should close the message queue every time the use it.


Could be.


> Does CygIPC have some error handling functionalities..


Not really.


> Say The IPC Service gets stuck when a pgm using message queues crashes..(for
> then the messages queues are not closed)


I dunno how you would solve this problem. (write programs that don't crash?)

*************
I host cygIPC at my website, cygutils.  I'll apply well-tested patches 
to it.  However, I didn't write the code; I've never really studied the 
GUTs of it -- and have no interest in doing so at this point.  (My 
hacking as mainly been around the edges, for usability and stuff).

Basically, further development of cygIPC itself is a dead end, and I 
don't want to waste much of my time on a dead end.  However, if somebody 
"out there" finds, debugs, and fixes any problems -- then I'll 
gratefully accept patches.  Caveat: IPC *client* code that follows 
published IPC interfaces (msgset, semget, etc) should be fairly portable 
among different IPC service implementations -- so developing IPC client 
apps on cygwin is NOT a dead end (see below).

Due to licensing issues outside my control, cygIPC cannot be included 
into the main cygwin distribution.  HOWEVER, it is possible that IPC 
functions MAY be added to the main cygwin, thus replacing cygIPC (that's 
why I consider cygIPC to be a dead end). Note: because of those pesky 
licensing issues, if you look at or study the cygIPC code, then you 
cannot participate in the process of adding IPC to cygwin itself. 
That's why I can't help add IPC to cygwin.
*************

--Chuck





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/