Re: simple test triggers fork errs for me in 4/27 snapshot

Thanks to all for trying the test. On Tue 5/16/06 21:20 PDT "Bryan D. Thomas" wrote: > >> If I revert to the April 3 snapshot it works fine. For the 4/27 > >> snapshot, it's repeatable > > > I see this under 20060309 as well. > > This is repeatable on my system with both 20060427 and 20060309 ve

Re: simple test triggers fork errs for me in 4/27 snapshot

On Tue, May 16, 2006 at 09:08:28AM -0500, Tom Rodman wrote: > If I revert to the April 3 snapshot it works fine. For the 4/27 > snapshot, it's repeatable, the commands above resulted in fork errors > when I tried it just after after a reboot today, and again after all > cygwin processes had been ki

simple test triggers fork errs for me in 4/27 snapshot

Below is a nonsense set of commands derived from a useful script that was getting fork errors w/the 4/27 snapshot: ~ $ date;uname -a Tue May 16 07:58:20 CDT 2006 CYGWIN_NT-5.0 OurServer108 1.5.20s(0.155/4/2) 20060427 13:16:59 i686 Cygwin ~ $ cd /tmp;echo -ne '#!/bin/bash -u\nfoo "$@"\n' >b