In ProTop 327, the default threshold for ProTop debug files is now set to 100 MB, which limits log file growth by default and adds a sequence to the logfile name.
The value is set in PROTOPDIR/protop.pf:
# this applies to logs created by -clientlog and LOG-MANAGER, not ALL logs
# if -logthreshold is set to a non-zero value then -numlogfiles defaults to 3
# and a sequence number will be automatically inserted into the logfile name
#
# -logthreshold 500000 # 0.5 MB, minimum allowed
# -logthreshold 100000000 # 100 MB, reasonable for ProTop client logs
# -logthreshold 1000000000 # 1.0 GB, seems way bigger than we should ever need
# -logthreshold 2147483647 # 2.0 GB, maximum allowed
-logthreshold 100000000 # 100 MB, reasonable for ProTop client Logs
CAUTION: The immediate effect for your ProTop installations once upgraded to 327 is that your ProTop debug log files (created by -clientlog and LOG-MANAGER), like dbmonitor.debug, found in PROTOPDIR/tmp, will now be named dbmonitor.000001.debug. And, there may be up to 3 of them. Please adjust any custom log management accordingly or comment out -logthreshold in etc/protop.pf.
Background and Justification
We've had cases of ProTop sessions being stuck in a loop and throwing repeated errors. This can quickly grow to GB of data and consume all available disk space. This approach caps the amount of disk space these logs can consume, preventing this situation from occurring by default.
See also:
Progress documentation on Log Threshold (-logfilethreshold).
Progress doc on Number of Log Files to Keep (-numlogfiles).