Server configuration

The following configuration parameters may be set in the server configuration file (goldd.conf).

Parameter	Description
accounting.mode [strict-allocation]	The accounting mode can be one of usage-tracking, notional-charging, fast-allocation, or strict-allocation. If usage-tracking is specified, charges will simply result in the creation of usage records with no charge value. No charge will be calculated and allocations will not be debited. If notional-charging is specified, a charge will be calculated and recorded with the usage record, but allocations are not debited. If fast-allocation is specified, usage records will be updated with charge amounts and allocations will be debited, but liens will not be used to protect the allocation from simultaneous use. If strict-allocation is specified, usage records will be updated with charge amounts and allocations will be debited, and liens will be used to protect the allocation from simultaneous use.
currency.itemization [false]	Enables (true) or disables (false) the storing of itemized charges to the Charge table for charge transactions.
currency.precision [0]	Indicates the number of decimal places in the resource credit currency. For example, if you are will be dealing with an integer billable unit like processor-seconds, use 0 (which is the default). If you will be charging dollars and cents, then use 2. This parameter should be the same in the goldd.conf and gold.conf files.
database.datasource [DBI:Pg:dbname=mam;host=localhost]	The Perl DBI data source name for the database you wish to connect to
database.password	The password to be used for the database connection (if any)
database.user	The username to be used for the database connection (if any)
event.scheduler [false]	Specifies whether the event scheduler is enabled (true) or not (false)
event.pollinterval [5]	The period in minutes that the event scheduler uses to check and fire events. The poll interval must divide evenly into the number of minutes in a day (1440).
log4perl.appender.Log.filename	Used by log4perl to set the base name of the log file
log4perl.appender.Log.max	Used by log4perl to set the number of rolling backup logs
log4perl.appender.Log.size	Used by log4perl to set the size the log will grow to before it is rotated
log4perl.appender.Log.Threshold	Used by log4perl to set the debug level written to the log. The logging threshold can be one of TRACE, DEBUG, INFO, WARN, ERROR, and FATAL
log4perl.appender.Screen.Threshold	Used by log4perl to set the debug level written to the screen. The logging threshold can be one of TRACE, DEBUG, INFO, WARN, ERROR, and FATAL
notification.deliverymethod [store]	Specifies which delivery method is used by default if unspecified
notification.duration [1209600]	Defines how long in seconds that stored notifications persist before being automatically deleted. The default is two weeks.
response.chunksize [0]	Indicates the line length in the data response that will trigger message segmentation (or truncation). A value of 0 (zero) means unlimited, i.e. that the server will not truncate or segment large responses unless overridden by a chunksize specification in a client request. The response chunksize will be taken to be the smaller of the client and server chunksize settings.
security.authentication [true]	Indicates whether incoming message authentication is required
security.encryption [false]	Indicates whether incoming message encryption is required
super.user [root]	The primary Moab Accounting Manager system admin which by default can perform all actions on all objects. The super user is sometimes used as the actor in cases where an action is invoked from within another action.
user.firstaccountdefault [true]	If set to true, the first account that a user is added to will become the default account for that user. This default value is true.

© 2014 Adaptive Computing