Re: execv and then socket: operation not permitted

2005-01-12 Thread Eric Hoffman
Thanks for the help! That's about the only significant change in about 37000 lines of C code of a legacy application dating back to 1998... quite a testimony to both the original programmer (not me!) skills and Cygwin conformance to standards. Cheers, Eric On Tue, 11 Jan 2005 13:20:15 +0100,

Re: execv and then socket: operation not permitted

2005-01-11 Thread Corinna Vinschen
On Jan 10 22:54, Eric Hoffman wrote: On Sun, 9 Jan 2005 13:19:53 +0100, Corinna Vinschen wrote: Could you please prepare a short testcase, only containing the necessary lines to reproduce the problem? I have attached 2 files to reproduce the problem. It is linked to the putenv() call and

Re: execv and then socket: operation not permitted

2005-01-10 Thread Eric Hoffman
On Sun, 9 Jan 2005 13:19:53 +0100, Corinna Vinschen [EMAIL PROTECTED] wrote: Could you please prepare a short testcase, only containing the necessary lines to reproduce the problem? Thanks, Corinna I have attached 2 files to reproduce the problem. It is linked to the putenv() call and

Re: execv and then socket: operation not permitted

2005-01-09 Thread Corinna Vinschen
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)

execv and then socket: operation not permitted

2005-01-08 Thread Eric Hoffman
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