CFEngine Help: Re: cf-monitord: "Internal limit 4: Buffer ran out of space constructing string (3970 > 3968)."

Forum: CFEngine Help Subject: Re: cf-monitord: "Internal limit 4: Buffer ran out of space constructing string (3970 > 3968)." Author: davidlee Link to topic: https://cfengine.com/forum/read.php?3,26891,26907#msg-26907 Thanks for the reply, Sigurd. (1) You say it is a bug. What bug number is it,

CFEngine Help: Re: CFEngine Help: Service promises and reload

Forum: CFEngine Help Subject: Re: CFEngine Help: Service promises and reload Author: davidlee Link to topic: https://cfengine.com/forum/read.php?3,26901,26908#msg-26908 A very definite "+1" on this request! Just over a year ago, as I was getting our local cfengine-3 config developed, the handlin

CFEngine Help: Re: cf-monitord: "Internal limit 4: Buffer ran out of space constructing string (3970 > 3968)."

Forum: CFEngine Help Subject: Re: cf-monitord: "Internal limit 4: Buffer ran out of space constructing string (3970 > 3968)." Author: zzamboni Link to topic: https://cfengine.com/forum/read.php?3,26891,26913#msg-26913 David, cf-monitord is the one that collects all system-monitoring metrics for

CFEngine Help: Re: CFEngine Help: memory exhausted error

Forum: CFEngine Help Subject: Re: CFEngine Help: memory exhausted error Author: passerby Link to topic: https://cfengine.com/forum/read.php?3,26355,26914#msg-26914 You've been using right recursion in your bison rules. This uses up bison's stack of tokens if you're parsing long lists. Solution: