Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Shared memory problem
Date:	Thu, 25 Aug 2005 16:04:54 +0100
MIME-Version:	1.0
In-Reply-To:	<BAY105-F3DA07A9E16532EE26B933AEAB0@phx.gbl>
Message-ID:	<SERRANOA5L0kvvvzFGf000002e3@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: CRAIG SORENSEN
>Sent: 25 August 2005 15:56

> I have attached the cygcheck file and a short program that I have copied
> from a tutorial online. I am compiling it as shown here:
> 
> gcc shm_write.c -o shm_write
> 
> There are no errors or warnings when I compile, but whenI go to run, it
> says "Bad system call".

  I can't remember it off the top of my head, but there's a parameter you
have to add in to your %CYGWIN% environment variable to actually *enable*
the cygserver functionality.

  Ah.  Found it.  From http://cygwin.com/cygwin-ug-net/using-cygwinenv.html

(no)server - if set, allows client applications to use the Cygserver
facilities. This option must be enabled explicitely on the client side,
otherwise your applications won't be able to use the XSI IPC function calls
(msgget, semget, shmget, and friends) successfully. These function calls
will return with ENOSYS, "Bad system call".


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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 -