The gkrellm package provides a graphical monitor of the current system state of the NST.
The gkrellmd daemon allows one to run the gkrellm client on a different computer than the one being monitored. This client/server design allows one to monitor MANY NST probes from a central location with less of a network load than if one were to project a locally running gkrellm process to a remote X display or VNC desktop.
By default, the gkrellmd daemon is not running at the time the NST is booted (and to be honest, we are not that certain as to how secure of a application this handy utility is). To enable the gkrellmd daemon, you need to complete the following steps:
Add a gkrellmd user to the system.
Specify what host(s) will be allowed to connect to
the service (by default, only localhost
connections are permitted).
Tweak the /etc/gkrellmd.conf
file if the default settings are not to your liking (this
step is optional).
Start the gkrellmd daemon.
The following command sequence demonstrates how one
might accomplish this assuming one wanted to permit ANY system
on the 192.168.0.0 network access to the
daemon:
[root@probe root]# useradd -s /bin/false gkrellmd
[root@probe root]# echo "allow-host 192.168.0.*" >> /etc/gkrellmd.conf
[root@probe root]# /etc/rc.d/init.d/gkrellmd start
Starting gkrellmd: [ OK ]
[root@probe root]#
Now that the gkrellmd process has
been started, you can access it from a different system by
specifying the --server HOST option to
gkrellm.
[pkb@salsa docs]$ gkrellm --server 192.168.0.101 &
[pkb@salsa docs]$
If the client can't connect to the server, you will
see the message: Unable to
connect.