From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] removing users
Date: Thu, 19 Jun 2003 14:39:28 -0400 [thread overview]
Message-ID: <1ed8992b4d189a4f14486a3a1559475d@plan9.bell-labs.com> (raw)
In-Reply-To: <20030619182445.GA6452@thefrayedknot.armory.com>
> so i should rename them all to some null user which is unable to log in?
Don't rename them all to the same thing.
That will just confuse you later. We don't
ever remove people -- we just turn off their
accounts on the auth server.
We had a spell where we renamed foo to usedtobefoo,
but we've basically given up on that too.
Russ
next prev parent reply other threads:[~2003-06-19 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 23:06 Andrew
2003-06-19 6:36 ` Fco.J.Ballesteros
2003-06-19 17:50 ` Russ Cox
2003-06-19 18:24 ` Andrew
2003-06-19 18:31 ` boyd, rounin
2003-06-19 18:39 ` Russ Cox [this message]
2003-06-19 18:43 ` Andrew
2003-06-19 18:51 ` Russ Cox
2003-06-19 19:08 ` Andrew
2003-06-19 19:11 ` Russ Cox
2003-06-19 18:48 ` jmk
2003-06-19 19:17 ` Scott Schwartz
2003-06-19 19:19 ` Russ Cox
2003-06-19 19:27 ` boyd, rounin
2003-06-19 19:30 boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ed8992b4d189a4f14486a3a1559475d@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).