We just discovered a problem with the v2.0 scheduler that can cause it to consume a CPU if you are using glib < 2.32. The symptom is that starting the scheduler will result in a cpu running at near 100%. This was reported and fixed by bapper. If you are having the same problem please let us know. We are trying to determine if we should build a new fossology scheduler package.
Thanks, Bob Gobeille _______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
