• hpt config error to logfile

    From Kai Richter@2:240/77 to All on Saturday, December 26, 2020 14:51:32
    Hello All!

    Could you please verfiy the following with the actual hpt version?

    I did a re-organization and yearly cleanup of the arealist and made a mistake.

    ###
    ~$ ./scan.cmd


    Area [HARDWARE.GER] defined twice
    Please correct above error(s) first!

    Area [HARDWARE.GER] defined twice
    Please correct above error(s) first!
    ###

    Within the hpt logfile there was no entry of anything.
    Because this is a background task i do not see the error message.

    Could you please check this with the actual hpt version? To reproduce the error
    simply copy one echoarea line to have two identical echoarea lines.

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

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Alexander Kruglikov@2:5053/58 to Kai Richter on Sunday, December 27, 2020 09:51:28
    Good ${greeting_time}, Kai!

    26 Dec 20 14:51, you wrote to All:

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

    What level of logs is configured in config?

    With best regards, Alexander.

    --- "GoldED+/LNX 1.1.5-b20180707" ---
    * Origin: 24 hours in a day, 24 beers in a case, Hmmm... (2:5053/58)
  • From Kai Richter@2:240/77 to Alexander Kruglikov on Sunday, December 27, 2020 11:20:46
    Hello Alexander!

    27 Dec 20, Alexander Kruglikov wrote to Kai Richter:

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

    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)