Unix Web Hosting for Developers

every five minutes. You will need a Web server on the machine running MRTG. You can use MRTG to give supervisors, managers, and co-workers convenient access to performance data without giving them server access. And, because MRTG keeps records over the course of a year, you can get a good idea of real-life trends. MRTG is also quite useful for justifying hardware and software expenditures, since you can point to exactly how much CPU time a machine is using, and how its performance has changed as you’ve added software. Configuring MRTG You can use the included cfgmaker(1) tool to generate a default MRTG configuration that measures network throughput on interfaces, like so: ………………………………………………………………………………………. # cfgmaker communityname@machine > mrtg.cfg ………………………………………………………………………………………. For example, if I wanted to run MRTG on my local machine, using the community name GetLostLoser, I could run this command: ………………………………………………………………………………………. # cfgmaker GetLostLoser@localhost > mrtg.cfg ………………………………………………………………………………………. Cfgmaker makes SNMP queries of the specified device and generates a basic configuration file, which we dumped into the file mrtg.cfg in the preceding example. By default, MRTG monitors only network traffic. Before you can use this configuration file, you need to add a “WorkDir” directive to the top of it to tell MRTG where to store its logs, graphics, working files, and HTML. I generally put the WorkDir somewhere under my Web server root directory, like this: ………………………………………………………………………………………. WorkDir: /usr/local/share/apache/htdocs/mrtg ………………………………………………………………………………………. You’ll probably want to password-protect this directory, too, if the Web server is on the public Internet or otherwise exposed to the world at large. (See Chapter 15.) Sample mrtg.cfg Entry The generated mrtg.cfg has a lot of information, including some unnecessary HTML. If you look through the created file, you’ll see that cfgmaker has generated a configuration for every single interface on the machine, which is proper because it measures network throughput by default. The loopback interface, and any down interfaces, are commented out; the remaining uncommented parts are a series of entries much like this: ………………………………………………………………………………………. vTarget w [localhost.3]: 3:GetLostLoser@localhost x MaxBytes[localhost.3]: 1250000 442

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Unix Web Hosting services