[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
|
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
925.0. "console archive consolemanager & SYSTEM-W-ACCONFLICT" by 54411::SYS_MJANSSEN (Marc Janssen (889-9594)) Tue Aug 15 1995 07:11
Hello,
I the following a normal "archive" behaveour:
JGODCC ->$ console archive consolemanager
POLYCENTER Console Manager
Archive facility Version V1.6-100
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Starting archive procedure for system ConsoleManager
%COPY-E-OPENOUT, error opening CONSOLE$ROOT:[LOG]CONSOLEMANAGER.TIMES;
as output
-RMS-E-FLK, file currently locked by another user
%COPY-W-NOTCOPIED,
DISK$JGOPCM_54794:[ARCHIVE]CONSOLEMANAGER_NEW.TIMES;1 not cop
ied
%SET-E-READERR, error reading CONSOLE$ROOT:[LOG]CONSOLEMANAGER.TIMES;1
-SYSTEM-W-ACCONFLICT, file access conflict
%COPY-E-OPENOUT, error opening CONSOLE$ROOT:[LOG]CONSOLEMANAGER.LOG; as
output
-RMS-E-FLK, file currently locked by another user
%COPY-W-NOTCOPIED, DISK$JGOPCM_54794:[ARCHIVE]CONSOLEMANAGER_NEW.LOG;1
not copie
%SET-E-READERR, error reading CONSOLE$ROOT:[LOG]CONSOLEMANAGER.LOG;1
-SYSTEM-W-ACCONFLICT, file access conflict
%COPY-E-OPENOUT, error opening CONSOLE$ROOT:[LOG]CONSOLEMANAGER.EVENTS;
as outpu
t
-RMS-E-FLK, file currently locked by another user
%COPY-W-NOTCOPIED,
DISK$JGOPCM_54794:[ARCHIVE]CONSOLEMANAGER_NEW.EVENTS;1 not co
pied
%SET-E-READERR, error reading CONSOLE$ROOT:[LOG]CONSOLEMANAGER.EVENTS;1
-SYSTEM-W-ACCONFLICT, file access conflict
Archive procedure for system ConsoleManager completed successfully
JGODCC ->$ dir console$archive:*console*/siz=all
Directory DISK$JGOPCM_54794:[ARCHIVE]
CONSOLEMANAGER.9412091330_TO_9412100130_EVENTS;2
153/153
CONSOLEMANAGER.9412091330_TO_9412100130_LOG;2
264/264
CONSOLEMANAGER.9412091330_TO_9412100130_TIMES;2
10/12
JGODCC ->$ dir console$logfiles:*console*/siz=all
Directory CONSOLE$ROOT:[LOG]
CONSOLEMANAGER.EVENTS;1
6788/6792
CONSOLEMANAGER.LOG;1
11762/11775
CONSOLEMANAGER.TIMES;1
867/942
In other words, the Archive was successful, but the logfiles area is
not cleaned for consolemanager files. This is not the case for regular
node-type of logfiles.
Thanks ,
Marc Janssen
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 925.1 | | 29067::BUTTERWORTH | Gun Control is a steady hand. | Tue Aug 15 1995 14:55 | 8 |
| Marc,
There is a restriction that you have to shutdown ConsoleManager
before you can actually Archive the ConsoleManager files themselves.
Regards,
Dan
|
| 925.2 | Hmmm, it's a pity... | 54411::SYS_MJANSSEN | Marc Janssen (889-9594) | Wed Aug 16 1995 05:53 | 12 |
| Hmmmm....
That's a pity, since we try to automate all maintenance activities in
a scheduler jobs.
I have added the "archive" command just before the console$Startup in the
system startup, to make sure the files will be archived at least during
a reboot.
I do not understand why this is possible for the reguler node-logfiles,
but not for the consolemanager files. Perhaps something for V 1.7 ?
Marc
|