X-Spam-Check-By: sourceware.org
Date: Fri, 2 Mar 2007 13:46:17 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
cc: cygwin AT cygwin DOT com
Subject: Re: Difference Between CYGIPC And CYGServer
In-Reply-To: <45E864DF.1060307@cwilson.fastmail.fm>
Message-ID: <Pine.GSO.4.63.0703021345130.2612@access1.cims.nyu.edu>
References: <20070302072040 DOT 4542 DOT qmail AT web7611 DOT mail DOT in DOT yahoo DOT com>  <45E864DF DOT 1060307 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, 2 Mar 2007, Charles Wilson wrote:

> neo napster wrote:
> > I have a few queries regarding cygserver and cygipc. what will be the
> > impact to move from cygipc to cygserver? I have some systems programs
> > which make calls to the CYGIPC, since these programs are coded long
> > back.
> >
> > Can you please give us an idea of the things that need to be done to
> > move from cygipc to cygserver. Our programs are coded in C.
>
> Both provide (some) of the standard IPC calls.  Both cygipc and
> cygserver implement the BSD interfaces for shared memory, semaphores,
> and message queues. (In cygwin-1.7.0+, cygserver will also implement
> POSIX-compliant shared memory objects and message queues).
>
> cygipc is practically unmaintained -- and the code quality is, er, less
> than ideal.  cygserver is actively maintained and coded to a much higher
> standard.
>
> Since both, today, implement the same BSD-derived interface[see (4),
> below], to move from one to the other, you should simply
>
> (1) stop using -I/usr/include/cygipc in your build
> (1) stop using -lcygipc2 in your build
> (3) don't run ipc-daemon2.exe; instead, run /usr/bin/cygserver-config
> and follow the instructions.
> (4) remove calls to
>       cygipc_set_err_handler
>       cygipc_get_err_handler
>       cygipc_set_debug
>       cygipc_get_debug
>       cygipc_tracing_enabled
>    cygserver uses Win32 event logging for error and debug handling, so
>    these hacks provided by cygipc are unnecessary.

It seems that this information (verbatim) would be very useful in
cygserver.README (or some other document in /usr/share/doc/cygserver).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/