Even better... why not help the developers by checking out the test framework, and when you find a bug, create a test that demonstrates the bug by failing, but which will also pass if the bug is gone.
-Dan On Jan 7, 2011, at 10:56 AM, Mike Svoboda wrote: > Well, Cfengine is a mature product, but there is new code being introduced > that causes bugs. > > Maybe since Linux seems to be the primary platform that the bits are > developed on, tested against, and packages provided for -- that seems to be > the most stable platform. > > I've been running Cfengine on Solaris x86 for a few months now, and I've hit > several bugs. Currently, my MPS which services 900 clients (splaytime set > to 50m, execution every 60m) I've hit issues with 3.1.1 and 3.1.2 on the > MPS. Any time the MPS starts to service 8-10 clients in parallel, > cf-serverd segfaults. So, I've got my clients running 3.1.2, and my MPS > stuck on 3.0.5p1. With the memory leaks in 3.0.5p1, cf-serverd will grow to > 3gb RAM usage over a week or so. I'm restarting the daemon nightly to deal > with this. > > My options are to either move my MPS to Linux and off of Solaris x86, or > keep my MPS on 3.0.5p1 until 3.1.3 is released and hope the segfaulting > issue with cf-serverd goes away. This is just one example. I've also hit > bugs with cf-promises spinning a single CPU to 100% utilization, memory > leaks, etc. > > That's not to say that I don't love what Cfengine is doing for me. Its a > great product, but, with any massive deployment -- you hit bugs. Increasing > the developer base sounds great, but providing the developers with the bug > reports from what we're hitting in production in an easy to do manner would > also be sweet. > > Cheers > Mike > > > On 1/7/11 9:21 AM, "no-re...@cfengine.com" <no-re...@cfengine.com> wrote: > >> Forum: Cfengine Help >> Subject: Re: Feature request: add a flag to enable bug reporting / automatic >> submission >> Author: bbomgardner >> Link to topic: https://cfengine.com/forum/read.php?3,20031,20039#msg-20039 >> >> Personally I think that introducing something like auto-bug submission into a >> mature project is in some ways an admission of unstable code. And I'd rather >> have development time spent on new features or other efficiency improvements. >> Just my opinion of course. >> >> That said, its not a bad idea. If Cfengine was just starting out I think >> implementing a robust bug reporting mechanism like you described would be a >> great investment over the life of the project. I would certainly enjoy using >> another way of troubleshooting any cfengine quirks. >> >> Not being a developer myself, I see the solution to more rapid bug fixes is >> to >> continue expanding the user base by creating more community resources. I >> think in this way we can aid Mark in recruiting more developers to the team. >> >> >> I hope I'm not jumping on your idea too hard. =) >> >> _______________________________________________ >> Help-cfengine mailing list >> Help-cfengine@cfengine.org >> https://cfengine.org/mailman/listinfo/help-cfengine > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
