X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 31 Mar 2009 13:24:27 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: execve issues, and execve with cygrunsrv Message-ID: <20090331112427.GC12738@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <49D0B0CD DOT 6050009 AT pocock DOT com DOT au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49D0B0CD.6050009@pocock.com.au> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 30 12:45, Daniel Pocock wrote: > > > Hi, > > I'm using the execve call in a UNIX program (which works successfully), > and now I am testing it with Cygwin. > > The program is using execve as a way to restart itself after receiving > SIGHUP. > > The child process started by execve seems to be unable to work properly, > I observe various errors: > - DNS lookups fail > - binding to UDP sockets fails Is that with Cygwin 1.5.25 or with Cygwin 1.7? If it's 1.5.25, could you try if this still occurs under Cygwin 1.7? Does this only happen when started from a native Windows process (cmd.exe or so) or does this also happen when started from Cygwin's bash? > Furthermore, I would like the process to become a service started by > cygrunsrv. Is it safe to use execve in a process started by cygrunsrv? Did you try? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/