This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

execv and then socket: "operation not permitted"


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]