Conference csc32::consolemanager

935.0. "Upgrade to v1.6-110" by 61017::TSG_TAS (Mr Mass) Tue Aug 22 1995 03:39

Folks

We have had some interesting times since we upgraded about ten days ago...

We also saw the monitor disconnecting... hang immediately after the upgrade, but
it has gone away and never returned.

If the hierarchical c3 interface is used with labels turned off, and one of the
icons is in just the wrong place so that if I choose, for instance, commands,
console manager, editor and the cursor ends up over this icon, then the label
for that icon gets turned on and won't be turned off, unless the interface is
restarted.

We also saw the problem with archiving that was fixed when BYTLM was increased.
But we have seen other problems with archiving to the extent that I havn't had a
full successful archive since the upgrade.

I had expected a command of the form

$ cons arch all/noconf/bef=...

to be unchanged. The archive appears to work, but closer inspection shows that
the files in CONSOLE$LOGFILES are the same siz as they were, and even after
files in CONSOLE$ARCHIVE are deleted I can extract data from within the
timeframe that has been archived. I checked the wording regarding the /delete
qualifier very carefully and came to the conclusion that my original
understanding that this was meant to delete the files in CONSOLE$ARCHIVE
immediately after archiving data and deleting this from the logfiles, was wrong.
Obviously the /delete meant that it would delete the data from the logfiles
after an archive, not the srchive files themsleves. So I /deleted. Well, I was
wrong about being wrong - I now had no archived data that I had just archived.

Interestingly, if I cons arch nodename/noconf/bef= it works as expected, archive
files are created, not deleted, and the archived data does not exist in the log
files. A command procedure with a console command per managed system would work,
but is suboptimal. Belligerent me wants to use the all keyword.

I thought I'd just prove this to myself once and for all, before I started
writing notes. So this morning I started an archive using the all word. Half way
through the archive process went into LEF and refused to move. The log shows
that an archive for the node had started, multiline window didn't show that the
current node was being archived, status/cont showed the current node as being
archived but no new or old files had been created in CONSOLE$ARCHIVE. I'm no
chess player, but it was obvious that I was one move away from checkmate. So I
made it and hoped... shutdown pcm, restart it, and we're stuck. PCM knows it's
being archived, and it's wrong. Reboot.

One really good thing about 1.6 is that the startup is now really fast - a big
help!

Tony Sherrard