9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] duplicate uid in fossil
Date: Fri, 22 Aug 2003 00:59:32 -0400	[thread overview]
Message-ID: <3156454f9568823244154cc065ee2f2e@plan9.bell-labs.com> (raw)
In-Reply-To: <EF13FAD4-D457-11D7-A9CA-000393A941BC@ar.aichi-u.ac.jp>

If you can recompile fossil somewhere, then just take that assert out.
The code for reading the users file strips out duplicates so only the first
instance will be used. Once the system is up you will have to write the
file back out with 'users -w' to permanently remove the duplicate. The
decision to automatically read the users file on opening main was arguably
wrong.

However, you are not supposed to be able to create duplicate entries
if you use the console commands - how did you do it?

On Fri Aug 22 00:21:29 EDT 2003, arisawa@ar.aichi-u.ac.jp wrote:
> Hello,
>
> I'm stupid enough to add a user that is already registered in fossil.
> The result is:
>
> hera# fossil/fossil -c '. '$v/flproto
> nuser 4
> diskThread 782
> fs->ehi 4789 fs->elo 1 active=76750
> got fs source
> got file root
> nuser 28
> duplicate uid 'alice'
> assert failed: box->nuser == nuser
> fossil 777: suicide: sys: trap: fault read addr=0x0 pc=0x0002a89f
>
> How can I remove duplicate uid?
>
> Kenji Arisawa


  parent reply	other threads:[~2003-08-22  4:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  4:20 Kenji Arisawa
2003-08-22  4:26 ` boyd, rounin
2003-08-22  4:45 ` andrey mirtchovski
2003-08-22  4:59   ` Kenji Arisawa
2003-08-22  4:59 ` jmk [this message]
2003-08-22  5:36   ` Kenji Arisawa
2003-08-22  5:43     ` jmk
2003-08-22  5:46     ` Kenji Arisawa
2003-08-22 14:14   ` Kenji Arisawa
2003-08-22 14:01     ` lucio
2003-08-22 14:37       ` andrey mirtchovski
2003-08-22 14:54       ` Kenji Arisawa
2003-08-22 14:39         ` lucio
2003-08-22  5:25 YAMANASHI Takeshi
2003-08-22 15:10 ` jmk

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=3156454f9568823244154cc065ee2f2e@plan9.bell-labs.com \
    --to=jmk@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).