Subj : hpt config error to logfile
To   : Alexander Kruglikov
From : Kai Richter
Date : Sun Dec 27 2020 11:20:46

Hello Alexander!

27 Dec 20, Alexander Kruglikov wrote to Kai Richter:

 KR>> If then there is no pointer in the logfile to correct the
 KR>> configuration error first then i'd like to suggest to add one.
 KR>> This applies to all kind of un-logged errors that are
 KR>> configuration critical.

 AK> What level of logs is configured in config?

Uh, default? I'll take a look...

$ grep LogLevel *
config:LogLevels        34567890ABCDEFGJKMNT
config:ScreenLogLevels  234567890ABCDEFGJKMNT

Hm, there must be something like documentation...

That's not default.
  Default value: 1234567890ABCDEF

Please keep in mind that this is hpt/fidoconfig 1.4.0-stable and that my question was to check this with the actual husky suite.

fidoconfig.info:

   The log levels are following:
1 - Program start, end;
2 - dupecheck
3 - linking messages
4 - scanning messages
5 - posting messages
6 - execute strings
7 - bundles, pkts, links, freqs, file routing, file attachs, msg packing
8 - areafix, relink, autocreate
9 - error messages (critical, usually exit on error)
0 - creation of file-flags
A - trivial error messages (print message and continue execution)
B - warnings & alerts
C - informational messages
D - statistics
E - summary
F - print program name & version
G - message send/sent
H - recoding operations & recoding tables read/write
I - Generate or check MSGID
J - Echomail phase
K - Filebox phase
L - Netmail phase
M - File create
N - File delete
O - operations with opened file (read, write, seek, ...)
P - Directory operations (create, delete, rename, ...)
Q - Email message parsing and construction
R - Truncate file
S - File send/sent
T - Test files (exist, permittions, etc.)
U - Functions calls (entering func & leaving it)
V - reserved
W - reserved
X - Filenames construction
Y - Link messagebase pass (some phase in hptlink & etc)
Z - debug messages: source lines (functions control points).
a-z - debug messages

My configuration error of duplicate echoarea definition was an exit on error and should be in the logfile with Level 9.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
 * Origin:  Monobox  (2:240/77)

.