9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] identity/ownership
Date: Tue,  6 Nov 2001 16:15:44 +0200	[thread overview]
Message-ID: <20011106161543.I25942@cackle.proxima.alt.za> (raw)
In-Reply-To: <20011106154506.H25942@cackle.proxima.alt.za>; from Lucio De Re on Tue, Nov 06, 2001 at 03:45:08PM +0200

On Tue, Nov 06, 2001 at 03:45:08PM +0200, Lucio De Re wrote:
>
> On Tue, Nov 06, 2001 at 01:44:03PM +0000, forsyth@vitanuova.com wrote:
> >
> > what are the non-comment lines in /lib/ndb/auth on the 3rd edition system?
>
> ----- cut here -----
> ----- cut here -----
>
I copied the 2ed /lib/ndb/auth to the 3ed fileserver, to seemingly no
avail.  This had me puzzled before, originally I had hostid=fickle in
the file, but after re-reading the documenttion decided to change it
to hostid=proxima, where fickle is the "sys" name for the CPU and AUTH
server (2ed) and proxima is the "owner" of the server.

For some peculiar reason, either seems to work with the 2ed
fileserver.  Is this possible?  Before I change the 3ed /lib/ndb/auth
to try again, can somebody point me to an authoritative statement as
to where the "hostid" really resides?

And, to repeat myself, why do I successfully access the 3ed filserver
from my workstation despite incorrect information in /lib/ndb/auth?

For the curious, the current values in /lib/ndb/auth are

	hostid=proxima
		uid=!sys uid=!adm uid=*

(indentation for effect, not in file).

++L


  reply	other threads:[~2001-11-06 14:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 13:44 forsyth
2001-11-06 13:45 ` Lucio De Re
2001-11-06 14:15   ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-07 14:22 presotto
2001-11-07 13:36 presotto
2001-11-07  9:03 Fco.J.Ballesteros
2001-11-07  9:12 ` Lucio De Re
2001-11-06 15:33 presotto
2001-11-07  5:27 ` Lucio De Re
2001-11-06 14:52 forsyth
2001-11-06 13:00 Lucio De Re

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=20011106161543.I25942@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).