Change in semantics: passing a max-size of 0 meant "unbounded (except for whatever internal bound cfengine itself imposes)"; unless we now change CfReadFile to interpret maxsize <= 0 as meaning "no bound on size", policies that specified a max-size of 0 are going to break.