Re: HBlink and DMRlink in "production"


Steve Siesel [K4KSA]
 

What should I change it to?

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, December 17, 2017 4:11 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] HBlink and DMRlink in "production"

 

See the log_handler info above...

On 12/17/2017 04:09 PM, Steve Siesel [K4KSA] wrote:

[LOGGER]

LOG_FILE: /var/log/hblink.log

LOG_HANDLERS: console-timed

LOG_LEVEL: DEBUG

LOG_NAME: HBlink

 

And the /var/log/hblink.log was created on the restart of HB_Bridge

 

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, December 17, 2017 4:08 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] HBlink and DMRlink in "production"

 

Post you logger stanza.

On 12/17/2017 04:07 PM, Steve Siesel [K4KSA] wrote:

Yeah I did see DEBUG after I hit send….I still did not add anything to the file….still 0 bytes

 

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, December 17, 2017 4:06 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] HBlink and DMRlink in "production"

 

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.
In that order. Though I will say for normal operation, DEBUG does not tell you much

On 12/17/2017 04:02 PM, Steve Siesel [K4KSA] wrote:

Right now its set for info….created a file…..Do I need to change INFO to something else for more detail?

 

From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Steve N4IRS
Sent: Sunday, December 17, 2017 3:51 PM
To: DVSwitch@groups.io
Subject: Re: [DVSwitch] HBlink and DMRlink in "production"

 

HBlink outputs a log. Check the LOGGER stanza for log file location and options.

 

 

 

Join main@DVSwitch.groups.io to automatically receive all group messages.