From: erik quanstrom <quanstro@quanstro.net>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] fscons users -r/-w <file> vs. editing /adm/users manually
Date: Sat, 15 May 2010 20:55:33 -0400 [thread overview]
Message-ID: <46c5b0cdfeddd4ffbe49588fc296ae20@kw.quanstro.net> (raw)
On Sat May 15 19:56:50 EDT 2010, corey@bitworthy.net wrote:
>
> If one wants to remove an existing user from the fossil file server,
> is it perfectly ok to simply edit /adm/users, as the hostowner user,
> directly? Or is it considered better practice to issue users -r/-w via
> fossilcons? Or is there effectively no real difference?
if you are using venti and thus have a dump (snapshots), i would
recommend against removing users since removing users can make
the dump unintelligible. at coraid, we just disable auth.
- erik
next reply other threads:[~2010-05-16 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 0:55 erik quanstrom [this message]
2010-05-16 1:16 ` Corey
2010-05-16 1:28 ` erik quanstrom
2010-05-16 2:34 ` Corey
2010-05-16 8:55 ` Steve Simon
-- strict thread matches above, loose matches on Subject: below --
2010-05-15 23:56 Corey
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=46c5b0cdfeddd4ffbe49588fc296ae20@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.net \
/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).