* Marc Haber > But it still hurts to have that done every five minutes. Additionally, > it is prone to confuse host-based IDSses which would need to be > manually configured to ignore the html files changing ctime and inode > all the time. Also, it breaks web caching.
Well, there's a reason for the name of the /var directory. If an IDS doesn't expect data in there to change, it's broken. And that it "hurts" to generate the HTML file is in my opinion a gross exaggeration, substituting some values into the templates and writing them out to disk asynchronously isn't an expensive operation either. I don't really know if the performance gain from using the stat+compare approach will be worth it - I've never seen a modern machine having any difficulty running munin-html. But I shall discuss it with Jimmy when he returns. > A fully-dynamic site is the optimum. Smokeping could serve as example. I agree, and I will try to convince Jimmy to implement that. :-) However it won't make it to the 1.2.x branch (too intrusive), but Etch is still far away so there's no rush. 1.4.x will probably be released sometime this summer, hopefully with the CGI capable of making the HTML pages as well. -- Tore Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
