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
Message-ID: <af67552e05010812586e656b9e@mail.gmail.com>
Date: Sat, 8 Jan 2005 21:58:09 +0100
From: Eric Hoffman <clallosy AT gmail DOT com>
Reply-To: Eric Hoffman <clallosy AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: execv and then socket: "operation not permitted"
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hi,

I am in the process of porting an application from Solaris/HP/Linux to Cygwin.
I manage to compile the whole lot. However, I encounter a problem at execution.

There is a first program (pserver) forking and launching an other one
(readhandler) through a call to "execv". However, within the second
one (readhandler), I get an error message on the first call to
"socket": "Operation not permitted".
When I launch the second one stand-alone with exactly the same command
line arguments it works OK.

So I suspect something with the permission - user associated with the
execv call. Note that within the fork, just prior to execv, the socket
allocation is working.

Any idea?

Thanks,

Eric

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