The 3 step process seems to be a long way around a very simple process.
If you are logging to the guest virtual console, just set the secuser for that
console to the PROP machine. As each line is logged to the console, PROP will
receive it and log it to disk. PROP automatically segments the CMS file at
midnight (and at PROP restart). I keep the PROP logs on a SFS directory. When
PROP can't access the directory, which happens when we do the FILESERV Backup,
we do loose the lines during that period.
When you want to look at the console for a particular machine, when in xedit
(in browse mode):
/* */
PARSE ARG USERID .
'SET SHADOW OFF'
'SET ZONE 19 26'
SELECT
WHEN USERID = 'ALL' THEN 'ALL'
OTHERWISE 'ALL /'USERID'/'
END
'BOTTOM'
'BACKWARD'
RETURN
To get into the PROP file (using SFS): (I have a mod 5 terminal)
FULLDATE = DATE('STANDARD')
FN = 'LG'SUBSTR(FULLDATE,3)
FT = 'ZVMV5R20'
'VMLINK .DIR OP1. <* * FORCERO> (NOTYPE STEM .FM)'
PARSE VAR VMLINK.1 . . FM .
QUEUE 'VERIFY 19 26 39 109 '
QUEUE 'CURLINE ON 2'
QUEUE 'PREFIX OFF'
QUEUE 'SET PF10 VERIFY 19 26 39 109'
QUEUE 'SET PF11 VERIFY 19 26 69 132'
QUEUE BOTTOM
QUEUE BACKWARD
'X ' FN FT FM ' (NOLOCK WIDTH 132'
'RELEASE ' FM
RETURN
Tom Duerbusch
THD Consulting
Law of Dinner Table Attendance
Cats must attend all meals when anything good is served.
>>> David Boyes <[EMAIL PROTECTED]> 9/25/2008 11:41 AM >>>
> 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
