From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <15330.217.127.226.4.1187390404.squirrel@webmail.kix.es>
In-Reply-To: <d1401a8d29292f63d54506990f3c6f30@plan9.bell-labs.com>
References: <52915.80.24.61.21.1187348619.squirrel@webmail.kix.es>
	<d1401a8d29292f63d54506990f3c6f30@plan9.bell-labs.com>
Date: Fri, 17 Aug 2007 15:40:04 -0700
Subject: Re: [9fans] Re: CPU Server
From: kix@kix.es
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
User-Agent: SquirrelMail/1.4.10a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: ac05bf7c-ead2-11e9-9d60-3106f5b1d025

Many thanks Geoff and Nemo,

this mail is very good for a newbee. I will check my network
configuration, now I have the sysname in plan9.ini.

I will start my holidays in a few hours, and I will no open my laptop for
a week.

Thanks!!!


> You can do things differently, but the way we do them is as follows.
> cpurc invokes cpurc.local and /cfg/$sysname/cpurc, where $sysname is
> the name of the current cpu server.  We intend that cpurc will be
> relatively static, cpurc.local should implement site-wide local policy
> (e.g., set cpu and facedom variables, run ipv6on) and
> /cfg/$sysname/cpurc should implement machine-specific local policy
> (e.g., run cron, httpd, dhcpd or tftpd).
>
> We consider it mandatory to set sysname.  If ndb/cs doesn't do it
> (perhaps because your /lib/ndb is imcomplete), you can set it in
> plan9.ini.  /n/sources/cfg/example/cpurc is an example cpurc; you
> might want to copy it to /cfg/$sysname/cpurc and edit the copy.
>
>