Undocumented Config Settings
From ARSWiki
Contents |
ar.conf
When reviewing the arstruct.h bundled with arserver 7.x, a number of undocumented ar.conf settings are enumerated. This section serves as a place to record people's experimentation with these undocumented configuration settings. There are also some undocumented (in documentation or c api header files) configuration settings. The full list of parameters is available in the Remedy api Trac application
Large-Result-Logging-Threshold
Enables loggging for large memory allocations due to large queries using GLEWF. The results of this setting are logged to the arserverd thread logs.
Syntax
Large-Result-Logging-Threshold: [bytes]
- bytes: threshold for logging memory allocation for GLEWF api calls
Example
Line breaks were entered for presentation, this would typically be a single line.
/* Tue Jul 01 2003 13:03:55.6420 */ Thread Id 2352 (GLEWF) large result - / Entries: 1000/Overflow memory: 88143/Pending file size: 73895/ RPC ID: 0/User: Demo/Form: xxx/
Track-Admin-Op-Progress
Thread-Debug-mode
Server-Security-Cache
Select-Query-Hint
RPC-Client-XDR-Size-Limit
Reduce-Checkpoint-Updates
arserverd (arserver.exe)
Startup Logs
ARServer has an undocumented flag, -t, that can be used to generate a startup log. To utilize this flag, update armonitor.conf/armonitor.cfg so that the line for arserverd/arserver.exe passes -t as a parameter. A log file will be created during startup in the db directory (same location as arerror.log). This has been verified on 7.0 (unpatched) on Solaris.
