Frans, this all sounds very strange indeed. I never heard that Cfengine would be able to harm any file because of corruption in transfer. If you kept the damaged file and that moment cfengine inputs by any change, it would be really good data to analyze. I've experienced some inconsistencies related to the way Cfengine prior to 3.1 handles text blocks, but I've never seen file damage of that kind you wrote about.
2010/11/9 Frans Lawaetz <fr...@broadinstitute.org>: > > On 11/09/2010 05:46 AM, Seva Gluschenko wrote: >> No, definitely. A file isn't installed in place of older one until >> it's copied succefully. >> > > Seva, that's what has me so alarmed. Like you and Neil pointed out, I > can take steps to minimize the odds of cf-serverd getting terminated > while engaged with clients but I see that as risk reduction to what is > otherwise a very severe bug. It does nothing to account for user error, > network glitches, or master host failures (assuming, again, that > cf-agent was thrown by the sudden termination of cf-serverd). > > *somehow* cf-agent modified my limits.conf file, ran into a problem (as > reported), and gave up, leaving me with a bricked system. I agree that > with copy-on-write, hashes, etc, this should be an impossibility but I > can only go by the sequence of events I initially posted. > > I will try to reproduce in lab although I think this will be very hard > to do. cf-serverd (3.0.5) used to segfault on me regularly and while it > made clients complain it never resulted in actual damage. > > Cheers, > Frans > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > -- SY, Seva Gluschenko. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
