Le 19/01/2010 18:33, Tim Cutts a écrit : > > On 19 Jan 2010, at 4:19 pm, Guillaume Rousse wrote: > >> Hello list. >> >> I'm trying to keep track of cfengine execution time, in order to monitor >> policy changes effect. >> >> The easiest way seems to add start/stop messages in the logs. >> >> If invocating cfagent from a cron task, it's quite simple, but doesn't >> allow to discriminate between update and main phase: >> 1 * * * * logger "cfengine start"; cfagent; logger "cfengine stop" > > Doesn't SplayTime make that a rather meaningless measurement? Indeed, good point. I'd have to be smarter there (or drop splaytime).
>> maybe they are better/easier ways to do it ? cfengine has a lot of >> files under its state directory, but none seems to have the relevant >> informations. > > cfshow -p > > can give you some performance information for particular parts of your > config, but doesn't seem to include the complete runtime. It gives performance measurement for each action individual action taken (provided you collect those informations of course), which allow you to get evolution of those individual actions over the time. But no way to compute the execution time of the last cfagent run :/ -- BOFH excuse #206: Police are examining all internet packets in the search for a narco-net-trafficker _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
