|
|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T V
Length: 1789 (0x6fd)
Types: TextFile
Names: »V«
└─⟦5f3412b64⟧ Bits:30000745 8mm tape, Rational 1000, ENVIRONMENT 12_6_5 TOOLS
└─⟦91c658230⟧ »DATA«
└─⟦458657fb6⟧
└─⟦a5bbbb819⟧
└─⟦this⟧
└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
└─⟦fc9b38f02⟧ »DATA«
└─⟦9b46a407a⟧
└─⟦eec0a994f⟧
└─⟦this⟧
-- Clean up persistent garbage generated by an RCG bug.
--
-- RCG (prior to D_12_4_8) had a bug whereby attributes associated
-- with Ada objects would accidently get created twice, with the first
-- collection of attributes becoming persistent garbage. Machines have
-- been found with more than 200 megabytes of persistent (i.e., undeletable)
-- garbage.
--
-- This utility will locate orphan attributes (known as attrs), and
-- optionally remove them. It can safely be run while others are using
-- the system, although it does require the caller to be a member of the
-- privileged group.
--
-- It typically takes 1 or 2 hours on an unloaded system to identify all the
-- ophan attrs, although on a heavily loaded system (or a system with many
-- Ada objects), it may take considerably longer.
--
-- The amount of disk space which can be reclaimed is summarized
-- by the utility; the reclamation will actually occur after the next
-- disk collection.
--
-- In VERBOSE mode, the locating of an attribute (good or bad) is
-- noted; this mode is not very meaningful for anyone other than a
-- low-level implementor.
--
-- In EFFORT_ONLY mode, bad attrs are not deleted.
--
-- Special notes:
--
-- 1. A message of "KEY_NOT_FOUND" is not fatal, and merely an indication
-- that some other job has started/completed on the system.
-- 2. A message of "NONEXISTENT_PAGE_ERROR" suggests the disk has
-- a corrupt object on it. This may or may not be fatal, and has
-- no known fix other than restoring from a 'good' backup.
--
-- In theory, this routine need only be run once after moving from a
-- pre-D_12_4_8 release to a post-D_12_4_7 release.
--
procedure Repair_Cg_Attrs (Verbose : Boolean := False;
Effort_Only : Boolean := True);