August 26, 2005

NLANR/DAST Multicast Beacon

Copyright (c) 1999-2005, The Board of Trustees of the University of Illinois.
All Rights Reserved.


KNOWN BUGS

* -make install- bug under Darwin

  There's a problem we're currently looking into with the 
  autoconf/make machinery under the Darwin OS that doesn't 
  perform the actual -make install- correctly.  The install
  appears to run correctly under all other OSs we've tested.

  The workaround is to go into the .../src directory after
  the -make install- successfully completes and run a 

		chmod +x beacon

  on the freshly made beacon executable.  You can now run
  it directly with

		./beacon

  there in the .../src directory or copy it to /usr/local/bin 
  or wherever else you like to put it on your path manually.


* True hostname of Central Server in beacon.conf bug

  There is also a bug in the TCP connection machinery for
  the TCP Central Server reports that currently requires
  you to use the true hostname of the Central Server you
  want to send reports to.  

  This is the CENTRALSERVERNAME setting in 
  .../src/beacon.conf.

  For example, the actual hostname for the alias of 
  "beacon.ncsa.uiuc.edu" we're using as the Central Beacon
  Server here at NCSA is "jhereg.ncsa.uiuc.edu".  For the
  moment, you must set 

		CENTRALSERVERNAME	= jhereg.ncsa.uiuc.edu

  to get your individual Beacons to connect correctly.
  The "beacon.ncsa.uiuc.edu" alias won't work at the
  moment.

