> > (assuming your Linux systems sent SYSLOG traffic to VM; mine do)
>
> Now how did you do that?
Sorry that I forgot to describe that side of it.
Edit /etc/syslog.conf and add a line something like
*.* @vmsysloghost
where "vmsysloghost" is a VM host running the aforementioned Pipeline.
You can have multiple @loghost lines giving the effect of a fan-out.
TAB characters are required. I've never understood why.
You will ALSO NEED to authorize the CMS v-machine running that pipe
to listen on UDP port 514 (as a server). I have stated things
simplisticly, but SYSLOG traffic really is easy to crunch.
As Dave Boyes mentioned, Neale (who wrote the mod for zipl
to cut a SYSLOG record, which initiated this thread) also ported
SYSLOG to OpenVM some years ago. Furthermore, Arty Ecock wrote
a VM SYSLOG in REXX with REXX/Sockets. Given a Pipelines based
SYSLOG utility (client, server, or both), that makes *three*
implementations of SYSLOG for VM.
-- R;
