Many thanks, Bill! That helps a lot.
I found the file wsjtx_syslog.log already, and I saw for example that it contains dozens of lines about audio dropouts. When CPU load of my computer is high, these lines occur more often (understandable) although all decodes seem to be displayed correctly. That brought me to the question, whether it is really necessary for all users by default to write such a line almost every cycle. I will do some tests with such an wsjtx_log_config.ini. Thanks, again! SYSLOG][2020-11-23 10:25:59.335369][02:45:06.360484][warning] Detected dropped audio source samples: 672 (0.014 S) [SYSLOG][2020-11-23 10:26:14.292842][02:45:21.317049][warning] Detected dropped audio source samples: -912 (-0.019 S) [SYSLOG][2020-11-23 10:27:29.160875][02:46:36.185177][warning] Detected dropped audio source samples: -528 (-0.011 S) [SYSLOG][2020-11-23 10:28:29.331624][02:47:36.355441][warning] Detected dropped audio source samples: -960 (-0.02 S) [SYSLOG][2020-11-23 10:28:44.321965][02:47:51.345443][warning] Detected dropped audio source samples: 672 (0.014 S) [SYSLOG][2020-11-23 10:29:14.267032][02:48:21.289967][warning] Detected dropped audio source samples: -768 (-0.016 S) [SYSLOG][2020-11-23 10:29:29.261178][02:48:36.284549][warning] Detected dropped audio source samples: 864 (0.018 S) [SYSLOG][2020-11-23 10:29:44.215267][02:48:51.238036][warning] Detected dropped audio source samples: -1056 (-0.022 S) [SYSLOG][2020-11-23 10:30:44.421766][02:49:51.444538][warning] Detected dropped audio source samples: 912 (0.019 S) [SYSLOG][2020-11-23 10:30:59.379238][02:50:06.401890][warning] Detected dropped audio source samples: -912 (-0.019 S) [SYSLOG][2020-11-23 10:31:29.310163][02:50:36.331803][warning] Detected dropped audio source samples: -1056 (-0.022 S) [SYSLOG][2020-11-23 10:31:59.289231][02:51:06.310913][warning] Detected dropped audio source samples: 1248 (0.026 S) [SYSLOG][2020-11-23 10:32:14.246623][02:51:21.268142][warning] Detected dropped audio source samples: -912 (-0.019 S) [SYSLOG][2020-11-23 10:32:29.233672][02:51:36.254892][warning] Detected dropped audio source samples: 528 (0.011 S) [SYSLOG][2020-11-23 10:32:44.191881][02:51:51.213443][warning] Detected dropped audio source samples: -864 (-0.018 S) [SYSLOG][2020-11-23 10:32:59.183405][02:52:06.204693][warning] Detected dropped audio source samples: 720 (0.015 S) [SYSLOG][2020-11-23 10:33:29.407386][02:52:36.428069][warning] Detected dropped audio source samples: -1104 (-0.023 S) [SYSLOG][2020-11-23 10:33:44.372188][02:52:51.393010][warning] Detected dropped audio source samples: -528 (-0.011 S) [SYSLOG][2020-11-23 10:34:14.467254][02:53:21.488220][warning] Detected dropped audio source samples: 6528 (0.136 S) [SYSLOG][2020-11-23 10:34:45.915297][02:53:52.935551][warning] Detected dropped audio source samples: 57936 (1.207 S) [SYSLOG][2020-11-23 10:35:02.682438][02:54:09.703075][warning] Detected dropped audio source samples: 3072 (0.064 S) [SYSLOG][2020-11-23 10:35:16.847555][02:54:23.867255][warning] Detected dropped audio source samples: -11328 (-0.236 S) [SYSLOG][2020-11-23 10:35:29.806666][02:54:36.826877][warning] Detected dropped audio source samples: 27648 (0.576 S) [SYSLOG][2020-11-23 10:35:46.819170][02:54:53.838629][warning] Detected dropped audio source samples: 28560 (0.595 S) [SYSLOG][2020-11-23 10:36:07.234210][02:55:14.254409][warning] Detected dropped audio source samples: 67584 (1.408 S) 73 de Uwe, DG2YCB Von: Bill Somerville [mailto:g4...@classdesign.com] Gesendet: Montag, 23. November 2020 12:51 An: wsjt-devel@lists.sourceforge.net Betreff: Re: [wsjt-devel] How to configure the new internal system and data logging facility? On 23/11/2020 09:43, DG2YCB, Uwe wrote: - A new internal system and data logging facility used to provide trace, debug, information, warning, error, and fatal error messages. The verbosity and filtering of messages is user definable via a configuration file. Without a configuration file a basic log is written with information, warning and error messages only. Log files are automatically rotated to limit disk usage. Hi Bill, How can I find information on such a configuration file for the new internal system and data logging function? Is there any documentation yet? Which parameters can be set and how? Is it also possible to deactivate the logging (to further reduce the number disk accesses)? I already looked in the online user guide but couldn't find it there. 73 de Uwe, DG2YCB Hi Uwe, an example user configuration file will be made available, for now you can see it here (note it needs some updates): https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/wsjtx_log_config.ini I would strongly advise not trying to turn off logging completely. The default settings with no configuration file are tuned for maximum performance and only write to the new wsjtx_syslog.log for messages of info status or higher. We will reserve those for occasional useful messages, warnings, errors, and fatal errors. The amount of disk access in that mode will be very small indeed. To configure the logging put a suitable wsjtx_log_config.ini in the WSJT-X log files directory. You might try this minimal configuration file to see what is actually logged at full verbosity: [Sinks.SYSLOG] Destination="TextFile" Asynchronous="true" AutoFlush="true" Format="[%TimeStamp(format=\"%Y-%m-%d %H:%M:%S.%f\")%][%Uptime(format=\"%O:%M:%S.%f\")%][%Channel%][%Severity%] %File%(%Line%) %Function%: %Message%" RotationTimePoint="12:00:00" Target="${AppLocalDataLocation}/logs" FileName="${AppLocalDataLocation}/wsjtx_syslog.log" TargetFileName="${AppLocalDataLocation}/logs/wsjtx_syslog_%Y-%m_%2N.log" Append="true" EnableFinalRotation="false" ScanForFiles="Matching" MaxSize=1073741824 MaxFiles="10" Note this is completely unfiltered and will write quite a lot of data, and is not recommended for normal operation. The configuration does this: * Creates a log message sink to a text file, * Writes to the file asynchronously in a separate thread (does not impact WSJT-X performance), * Flushes each message to the file immediately after they are produced (no buffering), * Formats the message with a timestamp, application uptime, channel, severity, code location, * Rotates the log file each day at midday, * Rotates old logs into the WSJT-X log files sub-directory "logs", * The log file name is wsjtx_syslog.log in the WSJT-X log files directory, * Rotated log files are named wsjtx_syslog_YYYY-MM_nn.log where nn is an incrementing number, * The existing log file is appended to on application startup, * Application startup scans existing log files and rotates them if necessary, * The rotated log files are limited to a total of 1 Gbyte or ten files. This is still a work in progress. The amount of log messages available and the channels they are written to will be expanded over future releases. Judicious use of channel and severity filtering will be most useful when creating custom logging configurations for diagnostics etc.. More information here: https://www.boost.org/doc/libs/1_74_0/libs/log/doc/html/log/detailed/utiliti es.html#log.detailed.utilities.setup.settings_file 73 Bill G4WJS.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
