Re: cygcheck triggers Wow6432Node infinite loop on Windows Server 2008

2009-06-25 Thread Corinna Vinschen
On Jun 24 15:30, Christopher Faylor wrote: > On Wed, Jun 24, 2009 at 02:00:52PM -0400, GJ Hagenaars wrote: > >Hi there, > > > >On a Windows Server 2008, running cronbug from the (bash) command line > >results in an ever increasing cronbug.txt file because cygcheck walks > >the registry and gets i

Re: cygcheck triggers Wow6432Node infinite loop on Windows Server 2008

2009-06-24 Thread Andy Koppe
2009/6/24 GJ Hagenaars: > Hi there, > > On a Windows Server 2008, running cronbug from the (bash) command line > results in an ever increasing cronbug.txt file because cygcheck walks the > registry and gets into an infinite loop. > > It will repeatedly find these entries, deeper and deeper in the r

Re: cygcheck triggers Wow6432Node infinite loop on Windows Server 2008

2009-06-24 Thread Christopher Faylor
On Wed, Jun 24, 2009 at 02:00:52PM -0400, GJ Hagenaars wrote: >Hi there, > >On a Windows Server 2008, running cronbug from the (bash) command line >results in an ever increasing cronbug.txt file because cygcheck walks >the registry and gets into an infinite loop. > >It will repeatedly find these

cygcheck triggers Wow6432Node infinite loop on Windows Server 2008

2009-06-24 Thread GJ Hagenaars
Hi there, On a Windows Server 2008, running cronbug from the (bash) command line results in an ever increasing cronbug.txt file because cygcheck walks the registry and gets into an infinite loop. It will repeatedly find these entries, deeper and deeper in the registry: Cygnus Solutions Cygnus