[9fans] Machine-specific cpurc customisation?

[9fans] Machine-specific cpurc customisation?

[Adrian Tritschler]

I was looking at the way I've set up my *enormous* (two PC) plan9 
network and thinking about adding changes to /rc/bin/cpurc. Since termrc 
includes termrc.local (if it exists), should cpurc include cpurc.local?

This would make it possible to have things like:

/rc/bin/cpurc

|...
|if (test -e /rc/bin/cpurc.local)
|	. /rc/bin/cpurc.local
|...

/rc/bin/cpurc.local

|...
|#global site-specific stuff, eg
|facedom=microsoft.con
|if (test -e /rc/bin/cpurc.$sysname)
|	. /rc/bin/cpurc.$sysname
|...

/rc/bin/cpurc.machine1

|# Machine-specific items for CPU/Auth machine "machine1"
|# for example
|auth/secstored >> /sys/log/secstored >[2=1] &
|#

The only problem I can see so far is that termrc.local is called before 
$sysname is available, but initialising the network in termrc.local 
should solve that.

If not, what other suggestions would people make on machine-specific 
configs, given that I'd like to be able to keep doing replica/pull from 
sources to stay up to date.

thanks,
	Adrian

---------------------------------------------------------------
Adrian Tritschler                          mailto:ajft@ajft.org
Latitude 38°S, Longitude 145°E, Altitude 50m,      Shoe size 44
---------------------------------------------------------------

Re: [9fans] Machine-specific cpurc customisation?

[Fco.J.Ballesteros]

We ended up with machine specific config to be run
before most of /rc/bin/*rc in some cases, and after
most of /rc/bin/*rc in other cases, sic.

The config to be run before is for those machines where
we need specific ipconfig lines, and the one to be run after
is for those machines where particular programs should run
after all of cpurc, sic.

What about doing something like this?

/sys/lib/sys/config/machine/rc:
	fn before() { blah blah }
	fn after() { blah blah }

/rc/bin/termrc
	test -e /env/fn#before && before
	blah blah
	test -e /env/fn#after && after

I just don't know of a cleaner solution, and, as probably
happen to you, I'm scared of facing toward the atrocity of
sys-v rc scripts.

Re: [9fans] Machine-specific cpurc customisation?

[Charles Forsyth]

i use a case on sysname in cpurc and compare updates on sources as they rarely occur.
i find it's easier to have everything in one file not scattered across
several. (the largest cpurc i've used had 13 cases with 5 architectures.)
default case * gives a `normal' general-purpose cpu server.