[3444] in SIPB bug reports
no room in the sipb locker
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Mon Jan 18 16:10:13 1993
Date: Mon, 18 Jan 93 16:09:52 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: web@Athena.MIT.EDU
Cc: eichin@Athena.MIT.EDU, bug-sipb@Athena.MIT.EDU
In-Reply-To: web@Athena.MIT.EDU's message of Mon, 18 Jan 93 15:55:00 EST <9301182055.AA06361@snorkelwacker.MIT.EDU>
From: web@Athena.MIT.EDU
Date: Mon, 18 Jan 93 15:55:00 EST
Too late. I already did it. I don't know that it needs to be discussed
by the whole sipb, but I did think it needed to have a second (and
third) opinion... which I got. for a long time now (over a year) there
have been lots of veto "oh.. but we SHOULD do this first..." well if
people REALLY believe that, then do it. but it hasn't been done. If
you (or other people) feel that other things should be nuked first, then
please do it.
Chee, you do next to nothing in terms of maintenance of the sipb
locker. You don't actively maintain many (if any) of the programs
currently installed in the locker, and you don't spend any time
working on cleaning it up or freeing up space in it.
Just where do you get off telling the people who *do* spend time
maintaining the locker what they should be doing, or sticking your
nose in and doing something significant to the locker before getting
those people to sign off on it?
To answer your question: I *have* been deleting unneeded tex/latex
files when space ran out. I don't have time to go through and figure
out *all* of the files that can be deleted, simply because I DON'T
HAVE TIME. If *you* wish to do something to alleviate the space
shortages, then do the *right* thing, not yet another stopgap measure.
I mentioned on the bug-sipb mailing list at least once that the next
space-freeing step should be to clean up unneeded tex/latex files.
That's what you should have done.
At the *very* least, you should have brought it up at a meeting before
doing what you did. No, I take that back, at the *very* least you
should have looked in the bug-sipb discuss meeting to find out who had
been active at clearing up space in the past, and contacted them about
what to do to clear up space now.
my call of what was important isn't based on how many people are using
xfish, or xneko, but of "how many people can't get work done if it were
unavailable during down time" my answer was lim x->0. I didn't make it
unavailable.... esentially I just extended the sipb locker quota (I put
it on the same partition as the project.sipb) and determined some of
which files athena replicates and which it doesn't. If you look at it
like that, I think it's perfectly fine.
I don't suppose "make install" in the source directories for the
programs you moved will do the right thing? The sipbsrc locker is
supposed to be kept in synchronization, as much as possible, with the
sipb locker. Hacks such as what you did make that nearly impossible.
jik
