|
Grex > Coop7 > #76: Suspending account deletions for August | |
|
| Author |
Message |
steve
|
|
Suspending account deletions for August
|
Jul 27 05:55 UTC 1995 |
At the board meeting tonight, we discussed the possibility of
suspending account reaping, since there are probably some college
students who have accounts here who haven't been on since the end
of school in April, and are in danger of getting reaped at the 90
day mark, which would be comming up soon.
Right now, we have had about 6 - 10 requests for protection from
the account zapper, and we've accomodated those folks--they won't
get killed for a long time (like until we remove them from the
immortals file). But, there are others who likely will get reaped
in the coming weeks.
The question is, should we suspent account reaping for something
like the month of August, and resume reaping at some point in
September? This would definately keep the accounts that will be
used once again around, but at the cost of keeping some 2,000+
"dead" accounts around, also.
We talked about this at the board meeting, but did not come up
with a definate answer, and wanted to present this here for
discussion.
|
| 44 responses total. |
rcurl
|
|
response 1 of 44:
|
Jul 27 06:02 UTC 1995 |
This response has been erased.
|
rcurl
|
|
response 2 of 44:
|
Jul 27 06:05 UTC 1995 |
To what extent are users informed of the 90-days-inactive reaping
policy, and how to have that extended for planned absences?
|
steve
|
|
response 3 of 44:
|
Jul 27 06:09 UTC 1995 |
I have to say that I'm against this idea. Grex already has
one of the more liberal account deletion policies on the planet,
and a lot of people don't expect something as long as a 90 day
period. While I am sympathetic to the idea that someone might
not want their account deleted, a) they can always be created
again (though there is a slight chance their login will be reused
by someone else), b) they could have asked us for an extended
period of time as some people did.
There are some technical reasons to not suspend reaping, too.
On average, each account reaped returns 17K of space back to
/var/spool/mail, thus making the approximately 2,000 accounts
not reaped during August add up to a rough total of 18M of disk
space that might not be available on the mail spool area.
Although other staff people don't agree with me on this, I
personally believe that the disk instability problems we've
had lately are somewhat related to the amount of space used on
/home, and not reaping accounts will (potentially) excerbate
that problem.
Programs like PicoSpan are slower for newcommers to run, since
PicoSpan has to wade through the passwd file, and more entries
means more time needed to plow through.
So, all-in-all, I'm of the opinion that while it would be nice
to be able to keep accounts around longer (remember when we didn't
reap for a whole *year*?), we're big enough that we really don't
have the resources to do this.
|
steve
|
|
response 4 of 44:
|
Jul 27 06:13 UTC 1995 |
Boy--it's pretty weird when you can't even enter the first
response in your own item. ;-)
A couple of notes on the math in #2: I mis-spoke myself at
the board meeting tonight, where I said that the reaped accounts
gave back an average of 50K/user. They *used* to do this, about
three months ago, but lately the average has been about 9K per
account reaped. Why people were more mail intensive before and
less so now, I can't say. Maybe people are heeding our pleas
not to subscribe to the HUGE-L mailing lists?
|
popcorn
|
|
response 5 of 44:
|
Jul 27 06:20 UTC 1995 |
Those pleas in newuser certainly help, and also I've started nuking the
accounts of the worst mail abusers, which should help lower the average
quite a bit.
Re 2: Users weren't really informed about the reaping policy in any clear
way until maybe 2 months ago, when I added some text to newuser that talks
about the reaping policy. I know we decided we wanted students to tell us
if they wanted their accounts to last through the summer, but I'm not sure
we ever found a way to clearly inform everybody that this was the policy.
|
robh
|
|
response 6 of 44:
|
Jul 27 10:00 UTC 1995 |
I have to agree with steve on this one. It won't be that
tough on the students who didn't ask, if they have to sit
through newuser once a year. And we can make the reaping
policy a little more visible, so there won't be a problem
next summer.
|
srw
|
|
response 7 of 44:
|
Jul 27 15:48 UTC 1995 |
I am one of the staffers who disagreed with STeve about this.
I believe the policy discriminates against students, especially those
whose only connection exists during the school year. We know that
there are many students on Grex, and yet we only have a handfule of
immortality requests.
I seriously question whether any reduction in disk-full accomplished
by reaping these students a month before they come back to school will
make any difference in our disk instability.
It is only the mail spool argument that I have any trouble refuting.
If we do proceed to do this reaping, then I think it should be
recognized that it is our hopelessly inadequate mail spool partition
that has forced it to happen. As a long term policy, this stinks.
We should serve the community, and I think this policy fails to do that.
|
carson
|
|
response 8 of 44:
|
Jul 27 19:46 UTC 1995 |
which community, Steve?
|
dam
|
|
response 9 of 44:
|
Jul 27 21:27 UTC 1995 |
How is it discriminatory when anyone can ask not to get deleted?
I'm sure if there is infinite disk space, no one would have to get deleted,
and they could keep collecting mail from mailing lists long after they call
for the last time. but, since there isn't infinite disk space, all the mail
they get and will never see is disk space that no one else can use.
since grex can't add a new hard drive every time the mail spool gets full,
and the majority of people who leave grex and never call again don't send mal
(mail) to staff telling them so, some people are going to have to get their
accounts deleted eventually.
|
sbj
|
|
response 10 of 44:
|
Jul 27 22:25 UTC 1995 |
This makes sense to me.
|
orwell
|
|
response 11 of 44:
|
Jul 27 23:43 UTC 1995 |
It seems that a logical way to avoid this dilemma next year is to certianly
post announcements beginning in April explaining to all users that they
should take certain steps to perserve their account till the next fall.
IT would be as easy as an e-mail message to each user. I say the people who
dont respond by a certain date, get theri acoounts nuked.
I agree that somone getting their account nuked wihtout prior notice
would be angry for a while, but it is just as easy to get a new account.
|
nephi
|
|
response 12 of 44:
|
Jul 28 11:00 UTC 1995 |
What would be the problem with moving the entire reaping schedule back a
month? If we move this reaping back to mid-September, then we could have the
next reaping happen three months later (mid-December), etc.
Doing it this way may make /var/spool/mail a little more uncomfortable for
a month and would definitely be a bit of a headache for Valerie (who generally
gets the "privilege" (8^) of moving people's mail out of there when it get's
too full), but I know about a hundred people at McKendree who would probably
ask to be put on the "immortals" list if it were to be publicized that they
would lose their accounts over the summer if they didn't. And McKendree
is just a drop in the bucket. What about U of M?
Which would become the bigger headache? Moving mail for a month or putting
hundreds of people on an immortals list?
|
popcorn
|
|
response 13 of 44:
|
Jul 28 12:20 UTC 1995 |
(Actually, STeve does reaps almost daily, not once every 3 months.)
According to the calculations someone did on the back of a napkin at the board
meeting, /var/spool/mail would be a *lot* more cramped for space, to the point
where I'd be limiting people to maybe 1/2 the amount of mail they can
currently accumulate before I move their mail to their home directories.
I'm willing to do the extra work to keep /var/spool/mail usable, in order to
avoid reaping these students during the last month of the summer. I'd like
to see us suspend reaping until mid-September.
|
steve
|
|
response 14 of 44:
|
Jul 28 12:39 UTC 1995 |
Ugh. Thats my only comment. ;-)
|
rcurl
|
|
response 15 of 44:
|
Jul 29 03:24 UTC 1995 |
I'd support extending the reap this time, but only because we have not made
our reap policy sufficiently well known.
|
srw
|
|
response 16 of 44:
|
Jul 29 05:13 UTC 1995 |
re 8: The community of all grex users. That includes those who have
lost access for the summer as well as the rest of us. Our current
reap policy is inconsiderate to a substantial portion of our users.
It makes more sense to suspend reaps for a month than to maintain
an immortals list. Who is responsible for removing people from that
list? Like any list it requires maintainance to be accurate. I say
cure the need for it (except for special cases that go beyond this
school-related timing situation).
|
marcvh
|
|
response 17 of 44:
|
Jul 29 16:44 UTC 1995 |
If the problem is mail spool space, why not nuke old mail (or move it to
people's home dirs) without purging the whole account?
(Actually, I'd like to see mailers that don't encourage maintaining mail
in the spool file, but that's another story.)
|
janc
|
|
response 18 of 44:
|
Jul 29 17:43 UTC 1995 |
Given a sound disk, I'd generally reap only when disk is getting low, and
then reap longest idle first until some standard amount of disk space was
freed up. Let accounts live as long as we can afford the space.
Given a flakey disk, who knows?
|
sidhe
|
|
response 19 of 44:
|
Jul 29 19:50 UTC 1995 |
Excuse me. Being a little extra-nice to our student-people
is not something that should even be debated. I've yet to
hear anything short of bitching over the idea that we'd be making
an exception for one month.
So what?
The "problems" it will cause are all hypothetical, until we
try it, and then, if it is a problem, we simply never do it again.
In the menawhile, anyone who's account is saved will be highly
appreciative of the thoughtfulness of grex, at this experimental move.
Maybe even enough to become a member.
|
scg
|
|
response 20 of 44:
|
Jul 30 00:38 UTC 1995 |
Um, the problems with the mail spool filling up are not at all hypothetical.
Staff -- mostly popcorn -- spends *a lot* of time that could be spent on other
moving peoples' mail when the mail spool gets too full. Even though popcorn
has said she's willing to do the extra work to keep the mail spool less full,
and in that sense the problem is solved, there will still be a lot of people
whose mail could otherwise stay in the mail spool who will find it being
moved, which probably will inconvenience them a bit. I support holding off
on reaping, but it is definately a tradeoff. After all, running newuser again
isn't that hard.
|
popcorn
|
|
response 21 of 44:
|
Jul 30 02:56 UTC 1995 |
(And the students whose accounts aren't reaped aren't going to be highly
appreciative. They won't notice. They'd only notice if they were reaped.)
|
steve
|
|
response 22 of 44:
|
Jul 30 08:43 UTC 1995 |
The problems we're talking about are hardly hypothetical. They
are extremely real.
|
sidhe
|
|
response 23 of 44:
|
Jul 31 22:15 UTC 1995 |
(odd-sided smile)
Or extremely virtual. This is cyberspace, after all.
Well, now, if thy read coop, they'll be appreciative. Also, would it
be inappropriate to welcome back the students in the MOTD, noting
as an aside, that their accounts had been specifically spared?
I still must believe the P.R. will be worth it.
|
jep
|
|
response 24 of 44:
|
Aug 3 07:50 UTC 1995 |
I know of one more reason for reaping accounts... people forget their
passwords, and then become frustrated when they can neither access their
old account or re-create it. I see this almost daily on M-Net. it's got
to happen on Grex, too.
I don't know how Grex handles lost password problems. I almost
invariably tell people they will have to create a new account, because
it's difficult to verify that spleen@somewhere.else.net, or even
spleen2@arbornet.org, is really the owner of spleen@arbornet.org. It
usually helps that I can tell them the spleen account will be reaped after
30 days if it's unused for that long, and that they can watch for it to
become available, and grab it again if they wish.
|