[31] in Release_7.7_team
Re: Expunging old files
daemon@ATHENA.MIT.EDU (dryfoo@MIT.EDU)
Tue Mar 15 11:36:59 1994
From: dryfoo@MIT.EDU
To: Kimberly Carney <kim@MIT.EDU>
Cc: "Richard Basch" <basch@MIT.EDU>, release-77@MIT.EDU, op@MIT.EDU,
In-Reply-To: Your message of Tue, 15 Mar 94 11:17:04 -0500.
Date: Tue, 15 Mar 94 11:36:32 EST
TWO POINTS:
Point #1)
} ...do expunging in users' dot files on log in.
I am worried about any method that can cause "a performance hit on log
in". How much of a hit? If there's one thing we know that our users
hate and are quite vocal about, it's long logins. Granted they're
willing to wait for horrendous amounts of cruft in their own .startups,
but anytime the system stuff gets noticeably long, we'll hear about it.
Also, does this mean that deleted files will get expunged always upon
the next login? or will there be some kind of date-checking involved?
That a user could blow away a file by logging back in to undelete gives
me the willies.
Point B)
This is just off the top of my head, but could something like this help
expunge work more quickly/efficiently: Could the delete command be
changed so that besides mv'ing the file, it maintains and modifies its
own small dotfile in the ~/, keeping just dates and deleted-file
locations -- kind of a path file for expunge to follow when it's
centrally invoked?
-- Gary
