| 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 |
There is a strange behaviour in the archive option of CONSOLE software.
On a DIGITAL-UNIX system (3.2) I start an archiving with the following command
# console -a -ALL -h -168 y (started on the 5th of February 1997 18:15)
(number of nodes approx. 10)
This should archive all stuff of the log files which is older than 168 hours to
the '/var/opt/console/archive/' directory, and leave the most recent 168 hours
into the system
But this command leave only the recent 48 hours in the system
(3-feb 18:15 to 5-feb 18:15) and that for all nodes.
The rest (29-jan 18:15 to 3-feb-18:15) was completely lost.
In the archive directory there should be stored all stuff from
(22-jan 18:15 to 29-jan 18:15)
but each of them contained only stuff from 22-jan 18:15 to 24-jan 18:15
the rest was completely lost.
Ingo Beele
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1481.1 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Feb 06 1997 11:25 | 13 | |
>This should archive all stuff of the log files which is older than 168
>hours to the '/var/opt/console/archive/' directory, and leave the most
>recent 168 hours into the system
Not quite. The command will archive the oldest 168 hours of data and
thats it. It does *not* mean that it will leave the newest 168 hours
of data. For example, let's say that it in the active logfiles of your
managed systems there is only 172 hours of data. When your archive
command completes there will only be the newest 4 hours of data left in
your active logfiles. (172 hours minus 168 hours = 4 hours).
Regs,
Dan
| |||||