From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] identity/ownership
Message-ID: <20011106161543.I25942@cackle.proxima.alt.za>
References: <20011106133824.4AAE3199BF@mail.cse.psu.edu> <20011106154506.H25942@cackle.proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <20011106154506.H25942@cackle.proxima.alt.za>; from Lucio De Re on Tue, Nov 06, 2001 at 03:45:08PM +0200
Date: Tue,  6 Nov 2001 16:15:44 +0200
Topicbox-Message-UUID: 16705b6e-eaca-11e9-9e20-41e7f4b1d025

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