Mail Archives: cygwin/2004/02/15/11:46:12
Looking at the cygwin sources, I realized that any access to cygserver is
disabled unless I explicitly export CYGWIN="server=1". Doing this
immediately solved my problems. Weird. Since cygserver is now the default
IPC code, shouldn't the default for allow_server be "yes"?
Frank
----- Original Message -----
From: "Frank Wübbeling" <wuebbel AT math DOT uni-muenster DOT de>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, February 15, 2004 8:06 AM
Subject: Re: Still trouble with IPC/cygipc
> Ok, I think I didn't make myself clear. I thought my trouble was somehow
> related to cygipc, but obviously it is not. I *do not* want to use cygipc.
I
> *do* want to use the new IPC routines in libcygwin.a.
>
> I startup cygserver (usually as a service, also tried it by hand) with log
> level 7 and debug enabled in cygserver.conf. Otherwise, cygserver.conf is
> unchanged. I get the usual startup messages, finishing with "waiting for
> requests". I compile an arbitrary program containing semget (ipc.h
includes
> cygwin/ipc.h, I checked that). I execute it, it dies saying "bad system
> call". In the logs of cygserver, I get absolutely nothing. Same thing on
XP
> (using that now) and Windows98. filemon says that no other files than
> cygwin1.dll are opened while my program is running.
>
> I feel completely lost here and have no idea what I could check to find an
> error.
>
> Frank
>
--
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 -