On Friday 16 May 2008 06:52, Randall R Schulz wrote:
...
Do you know why I'm not seeing the same complement of sensors on the remote client as on the local client for the same monitoring target?
Could it be this?: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- ## Type: yesno ## Default: no # # Enable mbmon support for gkrellm. # Requires the installation of the "mbmon" package as well # as mbmon being enabled as a daemon at startup. GKRELLMD_MBMON="no" -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- Unfortunately, if I set GKRELLMD_MBMON to "yes" I get a failure during daemon start-up: % /etc/init.d/gkrellmd restart Shutting down FOO done Starting gkrellmd Bad arg: --mbmon-port=12912 Interestingly enough, running strings on the daemon binary suggests that it does have that argument, but only accepts it under certain circumstances, which are not met on my system. The comment (above) says that installation of "mbmon" package as well, but I cannot find that package, so I guess I'll have to make do without being able to remotely monitor my GPU temperature (assuming this is why I cannot now do so). Anyway, setting the RECONNECT_TIMEOUT fixed the main problem of having to manually restart the client if the server is restarted. Thanks again. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org