[mrtg] customizing the index page

[Niall O'Reilly]

On 7 Mar 2008, at 20:02, PAUL WILLIAMSON wrote:

> Or use another frontend like routers2 or Cacti, each of
> which have their individual strengths and weaknesses.

	Or use HTML::Mason. Some effort is needed to get your head around
	it and to set up the main handler, but after that you may be able
	to avoid doing any maintenance on your index pages.

	I used to use a collection of SSI templates and 'make' to rebuild
	index pages to keep pace with changes made by our Network Team.
	It was 'unbegun work', as they say in Dutch.

	Nowadays, a Mason object is built from the same parameter file as
	we use to generate the related MRTG config, and than installed
	where it's needed as part of the process of activating the config.
	Index pages are built on demand and then cached.  From time to time
	I add a new view in the handler.  This is then immediately available
	for all relevant index pages -- no more visiting each directory
	where the index needs to be updated!


	Best regards,

	Niall O'Reilly
	University College Dublin IT Services

	PGP key ID: AE995ED9 (see www.pgp.net)
	Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.oetiker.ch/pipermail/mrtg/attachments/20080310/70af93ff/attachment.bin