Changes between Version 46 and Version 47 of GeniTmixTutorial


Ignore:
Timestamp:
03/05/13 11:14:54 (6 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixTutorial

    v46 v47  
    2222
    2323== 3 Run Tmix ==
    24 Now, run the following the following command on both nodes.  The script will set up the tmix.conf file correctly and configure the interface. 
     24Now, Make yourself root and move to the tmix directory by issuing the following commands on both nodes:
    2525{{{
    26 /usr/tmix/tmix-script.sh
     26sudo -i
     27cd /usr/tmix
     28}}}
     29
     30Next, run the following the following command on both nodes.  The script will set up the tmix.conf file correctly and configure the interface. 
     31{{{
     32./tmix-script.sh
    2733}}}
    2834You should see some output showing the actions, followed by "Done."
    2935
    30 Next, Make yourself root and move to the tmix directory by issuing the following commands on both nodes:
     36At this point, issue this command
    3137{{{
    32 sudo -i
    33 cd /usr/tmix/tmix
    34 }}}
     38cd tmix
     39}}}
     40to change to the /usr/tmix/tmix directory. 
    3541
    36 Tmix relies upon a pre-determined start time to synchronize tmix on the two noded.  On both nodes run the following command to determine the time and date:
     42Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes.  On both nodes run the following command to determine the time and date:
    3743{{{
    3844date
    3945}}}
    4046Note that the time may be in a different time zone. 
    41 Decide on a start time about 1-2 minutes in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes with 30 seconds to spare before that start time.
     47Decide on a start time about 2-3 minutes in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes with 30 seconds to spare before that start time.
    4248
    4349Finally, execute the following command on both nodes: