On 13/09/10 23:03, Steve Shipway wrote:
> In fact, we don't use daemon mode here, either.
>
> The reason for this is that, if using daemon mode, you need to use
> threading
or multiple daemon instances, each dealing with a different
collection of equipment.
> and then you lose control over the sequence in which
> Targets are processed
Good point, but partitioning the network between different
instances should help here too.
> -- I have some cfg files where separate Targets
> retrieve CPU user/wait/sys/idle stats and combine them to a graph.
> The first retrieve actually gets all 4 stats but caches the second
> pair, so I can be sure they are all in synch. If I used daemon mode,
> they might do both queries simultaneously.
Isn't this something the cache-access discipline should
protect against?
It seems there are quite a few different styles of using MRTG!
Niall
_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
