This is the mail archive of the
mailing list for the Cygwin project.
execv and then socket: "operation not permitted"
- From: Eric Hoffman <clallosy at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 8 Jan 2005 21:58:09 +0100
- Subject: execv and then socket: "operation not permitted"
- Reply-to: Eric Hoffman <clallosy at gmail dot com>
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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html