The following options are valid for FairPay's configuration files:

max_session_count

This option dictates how many instances of flipna may be executing external commands at the same time. This options is to prevent license user counts from being exceeded in any software with license managers, as well as to help throttle the load on a very busy system.

wait_interval

When flipna gets to the phase where it executes external commands, it performs a check to make sure that no more than a configurable number of instances of itself are doing so at the same time. If it detects that number are already running, it will retry the condition a configurable amount of times. This option sets the granularity for these retries. The argument is an integer expression denoting seconds. The default for this option is 1 second.

wait_attempts

The companion to wait_interval, this option denotes the number of retries to attempt before giving up and leaving the spool XML data file for the transaction in place for later perusal. The formula for total time spent retrying is wait_interval * wait_attempts. The default for this option is 600 attempts (10 minutes, given the default setting for wait_interval).

apache2

This option must be enabled with the Apache 2.x servers. Apache 2.x kills child processes whenever they close their main three file descriptors. This results in stranded files which would be cleaned under other web servers such as Apache 1.3.x. Set to yes if you are using Apache 2.x. Otherwise set to no, which is the default. If you set this to yes, please make sure your commands in the commands file are redirected somewhere harmless (/dev/null in *nix, for instance).

sandbox

This option dictates whether flipna will run its transaction validations against the PayPal Sandbox at PayPal Developer Central, or whether it will run its transaction validations against the live PayPal site. A setting of yes activates PayPal Sandbox testing mode. A setting of no enables live mode against the real site. (Note: As detailed in the official PayPal Integration Guide, transactions made in the Sandbox cannot be verified against the live site, and vice versa.

logging

This option dictates whether flipna and fairpay_sql_populate will log only fatal errors, or whether they'll log all transactions. A setting of yes enables logging of all transactions. The filenames in the fairpay directory are FLIPNA.LOG for flipna and FAIRPAY_SQL.LOG for fairpay_sql_populate.

log_size

This option sets the maximum number of lines in each logfile. If set to the word unlimited (or omitted), logs may grow infinitely. If set to an integer, logfile lines are kept to this many lines, with the oldest entries that exceed this threshhold being eliminated.

database_type

This option specifies which driver fairpay_sql_populate should use. The three supported options are MySQL, PgSQL, and ODBC.

database_host

This option tells fairpay_sql_populate which host to use for database population. A hostname or IP# is allowed.

database_name

This option tells fairpay_sql_populate which database name to use for database population. The database should contain the FairPay tables prior to use of.fairpay_sql_populate.

database_user

This option tells fairpay_sql_populate what username to use for database population.

database_pass

This option tells fairpay_sql_populate the password to use for database population.