> YES IMMENSELY. > Linux guests are our sole customer on /VM, so that is where my 'need to > know' lies.
Good. I have a personal interest in making sure BCBS gets this right. 8-) One other observation on DCSS: these are being exploited for Linux as containers to use for seldom-changed filesystems that are mounted on lots of systems. Mapping the contents of the filesystem into a memory block, and then mapping that memory block into multiple virtual machine's address spaces is really really clever, if a somewhat of a bear to manage. Great for /usr on mostly-identical systems, though. > I'm sure this wheel has already been discovered: Is there a 'doc' on > using > spool and a central 'syslog server' to capture Linux guest console logs? I think I did a presentation on it a few years back, which I can't put my hands on right now. I'll root around and see if I can find a copy. Basically the idea is threefold: 1) spool the virtual console of your Linux guest to another machine that acts as a collector for the files and processor and have it automatically close the console file every 750-1000 lines (or however much risk you're willing to tolerate). 2) configure /etc/syslog/syslogd.conf on Linux to log everything to /dev/console 3) Run PROP plus a homebrew exec in the collector machine that wakes up when a file arrives in it's virtual reader, reads it and sends each record to your central syslog server via UDP (or however you want them archived). Repeat forever. If you get an error in logging, save the incoming file and reorder it for later processing. Very easy, and quick to do. If I find the presentation, I'll put it up on the SNA www site and let you know where to find it. - db
