Re: syslog setup

On 6/23/2024 12:10 AM, Jim Duff wrote:

On 23/6/24 08:49, Arne Vajhøj wrote:

On 6/22/2024 5:57 PM, Jim Duff wrote:

On 23/6/24 03:23, Paul Coviello wrote:

Jim Duff wrote:

[Massive snip]

hmmm what was I expecting!  well it seemed pretty straight forward in the PDF that you set it up as it says and it just works, now after reading your comments there might be more I have to do.
>
I'll try it on Monday.
>
and the logger test message does work. just trying to get OPCOM to connect to it and hopefully your suggestions above I can figure it out

>
When you say "just trying to get OPCOM to connect to it" are you expecting that syslogd will somehow intercept your OPCOM messages and log them somewhere else?  Because it doesn't do that.
>
It takes syslog messages that match the priorities you have assigned to forward to OPCOM, in this case local1.err, and does exactly that, as I demonstrated in the example.

>
But if one want to send OPCOM messages to syslog then I assume one could:
* enable terminal as operator terminal
* run a little utility program that trap broadcasts
   and send them to syslog
?

 Sure, why not?
 https://www.eight-cubed.com/downloads.html#catch_opcom
 will trap the OPCOM messages, and it's a simple matter to open a datagram socket and write to the syslog port.

So to summarize and make sure that everybody sees the
same picture.
Normal flow:
application--->syslogd--->file
Builtin extra capability:
                        |->OPCOM
application--->syslogd-|
                        |->file
Not builtin extra capability:
             custom program<---OPCOM
                   |
                   v
application--->syslogd--->file
And it could be very unwise to combine:
              custom program<----|
                   |             |
                   v    |->OPCOM-|
application--->syslogd-|
                        |->file
Arne