Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 9 Jan 2005 13:19:53 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: execv and then socket: "operation not permitted" Message-ID: <20050109121953.GA5017@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jan 8 21:58, Eric Hoffman wrote: > 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? Could you please prepare a short testcase, only containing the necessary lines to reproduce the problem? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/