Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Protect against servers stepping on each other's toes
Date: Fri, 19 Oct 2001 23:35:39 +0200	[thread overview]
Message-ID: <vafhesvtis4.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)

If I have two servers using the same directory, there is potential for
the two stepping on each other's toes.

Here's a suggestion: when a server is first activated, it writes
something special to its directory which says what server `owns' that
directory.

But even before that, each server looks to see if some other server
has already written that the directory is `owned' by it.  When this
happens, a warning is issued or something like that.

Of course, given a directory d, all backends should use the same
method for `claiming' the directory; else they might trample on each
other's territory after all.

Also, maybe we want to put the claiming information inthe active
file.  Maybe in the directory _and_ in the active file?

Thoughts?
kai
-- 
GNU/Linux provides a nice `poweroff' command, but where is `poweron'?



             reply	other threads:[~2001-10-19 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 21:35 Kai Großjohann [this message]
2001-10-19 21:49 ` Paul Jarc
2001-10-19 22:37   ` Kai Großjohann
2001-10-19 22:46     ` Paul Jarc
2001-10-20 11:00       ` Kai Großjohann
2001-10-20  6:48     ` Matt Armstrong
2001-10-20 11:03       ` Kai Großjohann
2001-10-20 21:49         ` Matt Armstrong
2001-10-20 22:02           ` Kai Großjohann
2001-10-22  5:35       ` Paul Jarc
2001-10-22 16:54         ` Matt Armstrong
2001-10-22 20:05           ` Kai Großjohann
2001-10-19 22:42   ` Simon Josefsson

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=vafhesvtis4.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).