This is the mail archive of the
mailing list for the Cygwin project.
Re: execv and then socket: "operation not permitted"
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 9 Jan 2005 13:19:53 +0100
- Subject: Re: execv and then socket: "operation not permitted"
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Jan 8 21:58, Eric Hoffman wrote:
> 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?
Could you please prepare a short testcase, only containing the
necessary lines to reproduce the problem?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:email@example.com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html