deutsche Version

  Description
  Screenshots
  •   Version 0.1
  •   Version 0.3
  •   Version 0.5
  •   Version 0.7
  •   Version 0.8
  •   Version 0.9
  •   Version 1.0
  •   MOSIXLOAD
  •   MOSIXMEM
  •   MOSIXHISTORY
  •   main-window


  •   Download
      Known Bugs
      FAQ
      HowTo
  • Install
  • main-window
  • configuration-win
  • migrator-win
  • remote-procs
  • execution-win
  • MOSIXVIEW-client  
  • MOSIXCOLLECTOR
  • MOSIXLOAD
  • MOSIXMEM
  • MOSIXHISTORY

  •   Mailingliste
      Mirrors
      Thanks

       HowTo
       openMosix
       diskless-clients

       HowTo
       openMosix +
       MOSIXVIEW
       with SSH

      openMosix HOWTO

      www.openmosix.org

       SourceForge Logo

      thanks to freshmeat.net
    MOSIXVIEW
    Clustermanagment

    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, MOSIXMEM and MOSIXHISTORY (as described later) gives an nonstop overview of the load, memory and processes in your cluster. There is one main log-file called /tmp/mosixview/mosix.load. Additional to this there are additional files in this directory to which the data 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 or MOSIXMEM. 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:
  • mosixcollector -d      //starts the collector as a daemon
  • mosixcollector -k      //stops the collector
  • mosixcollector -c      //stops the collector and deletes the history-files
  • mosixcollector -n      //writes a checkpoint to the history
  • mosixcollector -r      //saves the current history and starts a new one
  • mosixcollector -help  //print out a short help
  • mosixcollector -h      //print out a short help


  • 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.



    next back