From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 30230 invoked from network); 2 Nov 2022 23:55:27 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 2 Nov 2022 23:55:27 -0000
Received: from maat.thinktankworkspaces.com ([45.79.94.76]) by 9front; Wed Nov  2 19:53:54 -0400 2022
Message-ID: <BA6C0B4DDB91772882BCF6D7C43E1CAF@thinktankworkspaces.com>
To: 9front@9front.org
Date: Wed, 02 Nov 2022 16:53:52 -0700
From: william@thinktankworkspaces.com
In-Reply-To: <79E17F00FA0C76BA833463939866386D@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: flexible stateless table deep-learning manager 
Subject: Re: [9front] Two file servers sharing an auth server
Reply-To: 9front@9front.org
Precedence: bulk

On a bigger note. I was curious about the users. Its nice to have a single auth
as mentioned by ori. But what's the bigger goal. Do you plan to have a lot of users. 
Do those users know basic unix commands to navigate around? What type of files
or media to you plan to serve?


Quoth ori@eigenstate.org:
> Quoth Nathan Zimmen-Myers <nathan@nzm.ca>:
> > As ori mentioned in IRC, keyfs is used to maintain the authentication
> > database which can be queried remotely (I believe? this might not be a
> > correct interpretation), is it correct to simply mount keyfs on web1
> > from fs1?
> 
> No; I thought you wanted to move or replicate the users between the
> auth servers.
> 
> > The other option which comes to mind, is to boot web1 from fs1, and
> > use web1's disk for documents to be connected to httpd, which may make
> > long-term maintenance easier. Would this be a more common
> > configuration?
> 
> Just give them the same auth server:
> 
> sys=foo ether=aabbccddeeff ip=1.2.3.4
> 	auth=1.2.3.4
> 
> sys=bar ether=aabbccddeeff ip=2.4.6.8
> 	auth=1.2.3.4
> 
> even better if you can share an fs, and
> therefore share the ndb, but you don't
> need to; just point at the auth server
> you want to use.
> 
> you don't even need to *own* that auth
> server, though you'll need the owner of
> the auth server to add a speaksfor line
> if your hostowner is different.
> 
>