Re: HBlink-HB_Bridge Logging

Cort N0MJS <n0mjs@...>

yeah, I did that and still have screwed up my own logging by forgetting it before :)

On Jun 29, 2017, at 10:04 AM, Steve N4IRS <szingman@...> wrote:

While we are highlighting things

On 6/29/2017 11:01 AM, Cort N0MJS wrote:
To point out the comments in the sample config file above the [LOGGER] section (emphasis added):

#   This allows the logger to be configured without chaning the individual
#   python logger stuff. LOG_FILE should be a complete path/filename for *your*
#   system -- use /dev/null for non-file handlers.
#   LOG_HANDERLS may be any of the following, please, no spaces in the
#   list if you use several:
#       null
#       console
#       console-timed
#       file
#       file-timed
#       syslog
#   LOG_LEVEL may be any of the standard syslog logging levels, though
#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones
#   used.

On Jun 29, 2017, at 9:47 AM, Steve N4IRS <szingman@...> wrote:

in hblink.cfg:
LOG_HANDLERS: console-timed or
LOG_HANDLERS: file-timed or
LOG_HANDLERS: console-timed,file-timed


On 6/29/2017 10:44 AM, G7RPG - Peter Kendall wrote:
Would it be possible to get a time/date stamp output in the logging for
HBlink-HB_Bridge ?


Cort Buffington

Cort Buffington

Join to automatically receive all group messages.