Sujet : Re: syslog setup
De : jim (at) *nospam* bad.invalid (Jim Duff)
Groupes : comp.os.vmsDate : 22. Jun 2024, 22:57:01
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v57hbe$3uebj$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Mozilla Thunderbird
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
thanks
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.
Jim
-- eight-cubed.com
syslog setup
Re: syslog setup