Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <002d01c3f3e3$328a8350$6402a8c0@humphrey> From: =?iso-8859-1?Q?Frank_W=FCbbeling?= To: Subject: Solved: Still trouble with IPC Date: Sun, 15 Feb 2004 17:45:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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" To: 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/