Excessive SSH Tunnel/Traffic
sverma at sfsu.edu
Sat Mar 15 02:56:52 GMT 2008
Jim Kronebusch wrote:
>> This would give us memory usage, cpu usage, network bandwidth and other
>> information from each thin client individually. This would hopefully be a
>> big help in diagnosing problems on thin clients. There would probably be
>> some tricks involved in automatically monitoring all thin clients (you
>> might need to set up static ips?).
> We already run fixed IP addresses and host name declaration with our setup so I did the
> sudo chroot /opt/ltsp/i386
> apt-get install munin-node
> vim /etc/munin/munin-node.conf
> add a second allow line with the IP of the munin server if it isn't the LTSP server
> vim /etc/hostname
> removed all lines in this file so it can build the hostname file based off the info
> that the dhcp server is providing
> Then on the munin server added hosts for the clients that boot up. It works pretty
> cool. Downside is it looks like ever client needs to be added individually.
Can you add an entire subnet in munin.conf (say, 192.168.89.0/24) I
don't have Munin setup on my LTSP lab, so I can't verify...at least not
until next week.
Dr. Sameer Verma, Ph.D.
Associate Professor of Information Systems
San Francisco State University
San Francisco CA 94132 USA
> It would
> be nice if munin would just sniff the network for hosts running munin-node and add them
> to the list automatically. At this point I would need to add lines for 107 other clients.
More information about the edubuntu-users