Mail Archives: cygwin/2007/03/02/13:46:39
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/
- Raw text -