This is an old revision of the document!
2 General FastPCRF parameters
| Parameter | Format | Default value | Description |
|---|---|---|---|
| daemon | bool parameter | 0 | Startup Mode: if daemon=1 then FastPCRF will be launched as a daemon. This parameter can be overridden by the –d command-line option. |
| verbose | bool parameter | 0 | Specifies detailed log level: if verbose=1, then program will log its actions verbosely,i.e. incoming requests and outgoing data; log level is specified by the trace parameter (see further). The default value is 0. trace – tracing bitmask; specifies the components to be verbosely logged. |
| trace | bool parameter | 0 | Tracing bitmask;specifies the components to be verbosely logged. Flag values see in logging. |
| rlimit_fsize | bytes | 1073741824 | Maximum log file size. |
| print_stat_period | seconds | 300 | Output period of internal statistics wtitten to the fastpcrf_stat.log file |
| work_thread_count | number | 5 | The number of working threads. It can not be configured by the user, since the number of working threads can not be more than the number of internal FastPCRF components for the moment. |
| async_queue_size | bytes | 524288 | The size of internal asynchronous message queue. Can not be configured by the user. If its size is too small, you may lose internal calls between components, amounting to a functionality loss and/or memory leakage. |
Was this information helpful?