Description Download FAQ HowTo Known Bugs HowTo MOSIX/diskless-clients HowTo MOSIX/MOSIXVIEW with SSH HowTo set up a Mosix cluster using Debian MOSIXVIEW Mailingliste |
MOSIXVIEW
Clustermanagment |
![]() |
|
the MOSIXCOLLECTOR
The MOSIXCOLLECTOR is a daemon which should/could be started on one cluster-member. It logs the MOSIX-load of each node to the directory /tmp/mosixview/* These history log-files analyzed by MOSIXLOAD (as described later) gives an nonstop overview of the load in your cluster. There is one main log-file called /tmp/mosixview/mosix.load. Additional to this are one file per clusternode to which the load is written. At startup MOSIXCOLLECTOR writes its PID (process id) to /tmp/mosixcollector.pid. It won't start if this file exist! The MOSIXCOLLECTOR-daemon restarts once a day (depending on when started) and saves the current history to /tmp/mosixview[date]/* These backups are done automatically but you can also trigger this manual. There is an option to write a checkpoint to the history. These checkpoints are graphically marked as a blue vertical line if you analyze the history log-files with MOSIXLOAD. For example you can set a checkpoint when you start a job on your cluster and another one at the end.. Here is the explanation of the possible commandline-arguments: You can start this daemon whith its init-script in /etc/init.d or /etc/rc.d/init.d. You just have to create a symbolic link to one of the runlevels for automatic startup. How to analyze the created logfiles is described in the following MOSIXLOAD-section. ![]() ![]() |