Path: ...!feeds.phibee-telecom.net!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Coviello <pcoviello@gmail.com>
Newsgroups: comp.os.vms
Subject: Re: syslog setup
Date: Mon, 24 Jun 2024 08:07:56 -0400
Organization: A noiseless patient Spider
Lines: 45
Message-ID: <v5bnk0$tv7h$1@dont-email.me>
References: <v4cp7a$1pet4$1@dont-email.me> <v4cvnf$1qm70$1@dont-email.me>
 <v4d1gh$1r26g$1@dont-email.me> <v4q8he$u3f8$1@dont-email.me>
 <2ef65812-45fb-bb91-6ac2-2cfbdcceb1de@gmail.com>
 <v4uhn1$1v7ke$1@dont-email.me> <v4ujel$1s53r$2@dont-email.me>
 <v53r5b$35kl2$1@dont-email.me> <v550js$3cc3a$1@dont-email.me>
 <v571c2$3ru2d$1@dont-email.me> <v57hbe$3uebj$1@dont-email.me>
 <v57kdk$3vfuj$1@dont-email.me> <v5876v$5t9j$1@dont-email.me>
Reply-To: azhrei1@yahoo.com
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Jun 2024 14:08:32 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="80e1e48c0cb7671ae124cbe5b4702395";
	logging-data="982257"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+60/LcZ2XOIrSaGzC4ADHA"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.18.2
Cancel-Lock: sha1:Dg/7v/eOLCkdrNaZa3m30lA4JTk=
In-Reply-To: <v5876v$5t9j$1@dont-email.me>
Bytes: 3043

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
>> ?
>>
>> Arne
>>
> 
> 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.
> 
> Jim.

Hi Jim I just downloaded the zip file and out of curiosity do I need 'C' 
to run this?