Re: lastseen confusion

> Which "updated doc" did I get early access to? I have searched the docs I The one you got the example from. > know of without finding too much on cf-report, but maybe I overlooked > something? And I will happily joint in thanking the team, but there is > always room for improvement. That is ve

Re: lastseen confusion

On 2 March 2010 12:23, Mark Burgess wrote: > > What I sent you was quoted from the docs. The problem with docs is both > when there is too > little and too much. > > Yes, I know what you sent me - I pasted the referenced text into the test file I used and it worked fine, I just needed at little p

Re: lastseen confusion

What I sent you was quoted from the docs. The problem with docs is both when there is too little and too much. M Erlend Leganger wrote: > On 2 March 2010 10:48, milo...@gmail.com > mailto:milo...@gmail.com>> wrote: > > > > This hasn't been released yet, so it s

Re: lastseen confusion

On 2 March 2010 10:48, milo...@gmail.com wrote: > > > This hasn't been released yet, so it seems for me the guys work hard > to update they doc and Mark gave you an early access to the updated > doc. > > Which "updated doc" did I get early access to? I have searched the docs I know of without fin

Re: lastseen confusion

> Why not include this in the documentation, then I wouldn't have had to ask > these all these questions? On the top of this page: Cfengine 3.0.4 This hasn't been released yet, so it seems for me the guys work hard to update they doc and Mark gave you an early access to the updated doc. Thank y

Re: lastseen confusion

On 1 March 2010 17:50, Mark Burgess wrote: > > I take the example in the reference manual > > http://www.cfengine.org/manuals/cf3-reference.html#control-reporter > > and run it: > > cf-report -f ~/tmp/cftest.cf > > Then I open the html page produced /tmp/nerves/last-seen.html > > Peers as last se

Re: lastseen confusion

I take the example in the reference manual http://www.cfengine.org/manuals/cf3-reference.html#control-reporter and run it: cf-report -f ~/tmp/cftest.cf Then I open the html page produced /tmp/nerves/last-seen.html Peers as last seen by atlas This report was last updated at Mon Mar 1 17:43:51

Re: lastseen confusion

On 26 February 2010 13:18, Mark Burgess wrote: > > I don't know what "in transition" means. The last seen report is available in > community. > Select a report type like html and and output directory (default > /var/cfengine/reports) > > M The term "in transition" is a quote from an unanswered

Re: lastseen confusion

I don't know what "in transition" means. The last seen report is available in community. Select a report type like html and and output directory (default /var/cfengine/reports) M Erlend Leganger wrote: > On 26 February 2010 10:05, Mark Burgess wrote: >> I think I wrote about it in a special t

Re: lastseen confusion

On 26 February 2010 10:05, Mark Burgess wrote: > > I think I wrote about it in a special topics guide on reporting... > I guess this is the link to that guide: https://cfengine.com/inside/document/SpecialTopic_Reporting.pdf But it didn't help me, it mentions cf-report once and lastseen once, bo

Re: lastseen confusion

I think I wrote about it in a special topics guide on reporting... Erlend Leganger wrote: > On 26 February 2010 08:48, Mark mailto:m...@iu.hio.no>> > wrote: > > It works perfectly here > > > Mark > > > Good, but I don't know how to use and I can't find any documentation on > it. Wher

Re: lastseen confusion

On 26 February 2010 08:48, Mark wrote: > It works perfectly here > > > Mark > Good, but I don't know how to use and I can't find any documentation on it. Where is cf-report documented? I tried the cf3-reference, cf3-tutoial and cf-report --help, but couldn't find a good description of how to use

Re: lastseen confusion

2010/2/24 > I've configured the reported to include last_seen. > body reporter control { >reports => { >"audit", >"performance", >"all_locks", "active_locks", >"hashes", "classes", >"last_seen", >"monitor_now", >"monitor_history", >

lastseen confusion

I've configured the reported to include last_seen. body reporter control { reports => { "audit", "performance", "all_locks", "active_locks", "hashes", "classes", "last_seen", "monitor_now", "monitor_history", "monitor_summary"