From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <14efc521ec54434e976b6c7ae5e0ae1b@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon,  7 Sep 2009 13:52:48 -0400
To: 9fans@9fans.net
In-Reply-To: <6A6A1524-95C8-4F5E-B0BE-11A11BC83F91@cs.ioc.ee>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] problem logging into a combined auth/cpu/fileserver
Topicbox-Message-UUID: 6949b8e8-ead5-11e9-9d60-3106f5b1d025

> 1. A simple example for a combined cpu/auth server, the 192.168.1.100
> machine, could be:
>
> ipnet=mynet ip=192.168.1.0 ipmask=255.255.255.0
> 	auth=bouncer
> 	cpu=cycles
> 	dns=lookup
> 	dnsdom=9fans.net
>
> authdom=9fans.net auth=bouncer

assuming that you mean authdom=myauthdom here,
and that "lookup" is actually an ip address, or
you have an entry for lookup like so
sys=lookup dom=lookup ip=ipaddress
i would think that you would also want to add
	authdom=myauthdom
to your ipnet.  this helps ipquery(8) and ndbipinfo(2)
find your auth domain correctly based on ip.

the example on the wiki may need updating.

> hostowner or other user). However having booted the terminal in this
> way I can only cpu to bouncer if I booted as bootes (the host owner)
> otherwise I get the following error message:

are you running auth/factotum (factotum(4))?

- erik