You have several options. First, Linux syslog: You can set the Linux system's syslog to feed your central syslog server. Most (not all) of what gets thrown on the console will then go there.
Second, CMS Pipelines: You can slurp the console traffic via SCIF (aka: SECUSER) into a pipeline running in another virtual machine and feed that through the UDP stage to your central syslog server. Third, PROP and REXX Sockets: You could use PROP (again in another virtual machine) with an action routine to deliver console traffic from the to-be-watched guest via REXX Sockets (UDP) to the central server. All of these are standard equipment (syslog on Linux, Pipelines and PROP on CMS). PROP is typically running on your OPERATOR virtual machine anyway. (Some would say PROP is therefore the easiest to enable for this task. I would say that Pipelines is the easiest on the eyes, though Linux syslog is a one-line change to /etc/syslog.conf.) -- R; <>< () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments On Mon, 25 Feb 2008, Patrick Spinler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > A question for all you good folks. We'd like to forward our linux > guest's console spools to a workgroup wide syslog server. > > Does anyone know of any code that could send syslog messages from a VM > service machine? > > Thanks, > - -- Pat > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHwwIqNObCqA8uBswRAg80AJ9ApbXg+60T4jSCNYFkr/AWCdkT0QCeJfDg > Tmf9q46UpNnfiLKz6ir6XKM= > =+b1D > -----END PGP SIGNATURE----- >
