Ticket #75 (closed defect: fixed)

Opened 3 years ago

Last modified 1 year ago

Is a config file necessary for the Fountain node daemons?

Reported by: samm Assigned to: samm
Priority: major Milestone: ICPADS06
Component: Fountain Version:
Keywords: config file Cc:
Blocking:

Description

When DEBUG mode is disabled, the Fountain node daemons probably don't need a config file. The only information they use from it is the name and port of the master Fountain daemon. We could easily provide this information in the form of a command line argument through the Fountain init script.

If DEBUG mode is enabled, it probably still makes sense to keep a log file in /tmp/fountain/<pid>/ since the information will be useful to fix bugs.

Change History

04/21/06 23:05:49 changed by samm

  • status changed from new to closed.
  • resolution set to fixed.

(In [315]) Fixes #37, #71, #75. I removed the common code shared between the master and slave Fountain daemons and added specialized code for each. Both the slave and master Fountain daemons no longer use a config file. The slave daemons now require a --host and --port argument to specify the master node's hostname and listening port. I may fix this to use an environmental variable for testing purposes since entering both parameters for every fountain node launched is somewhat tedious. The slave daemons also no longer use a logfile when FOUNTAIN_DEBUG is disabled. The calls to the qLog object are still present, the just do nothing since both screen and file output are disabled. When FOUNTAIN_DEBUG is enabled, a logfile is writtein in /tmp/<pid> where <pid> is the Fountain daemon's pid.

The master daemon writes its logfile in /var/log/fountain/master when FOUNTAIN_DEBUG is disabled, and /tmp/<pid> when it is enabled.