Hi Ray, I just grabbed the source from the cygwin cvs, tared and uploaded it. On the system I used it took <7 minutes.
http://repo.fossology.org/simpleIndex.php?mod=nomoslicense&show=detail&upload=148&item=50608165 We have seen the scheduler problem you describe before. I think, as long as you aren't hitting some system resource, stopping the scheduler and restarting it might take care of the problem (btw, v2.0 has a new scheduler). Bob On May 23, 2011, at 6:31 AM, Westphal, Raymond W wrote: > > On Friday my customer uploaded Cygwin for analysis. I think it was a zip > file. The job ran from 11:23am until I deleted it at around 8am on Sunday. I > had to delete it because it caused Fossology scheduler to keep restarting. > And that was causing the load average on the server to slowly climb. > > Has anyone had any experience with analyzing Cygwin? >
_______________________________________________ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
