From: David C. <da...@da...> - 2002-11-04 23:17:42
|
Net Llama! wrote: > 1) admin_uml: is this assuming that 1 UML instance with the arbitrary > name that i specify for this option will act as the 'admin' for all the > others running umld? admin_uml is the UML your UMLd calls to perform operations on UML filesystems (e.g. generate COW files, etc) - I probably need to rename this to build_uml. > 2) min_uid & admin_iud: i don't underestand what either of these specify admin_uid is a space seperated list of UIDs which are considered to be 'admin' users on your system. For example, I'm UID 500 here, so I put: admin_uid = 500 which means when I authenticate as the user 'david', I can perform operations on any UML even if it's not 'mine'. min_uid is used to define the lowest UID which can authenticate with UMLd - It is also used as some of my UMLs run as UID 98 and require non-standard options, so this is my bodge for that. > 3) distro: what is this? A directory containing distribution filesystems used for building COW files. > 4) cache: what is this? A directory used to cache root filesystems between UML builds. > 5) [secrets]: what's the difference between each of the 3 of them? admin = Secret for authentication as 'admin' user. Useful for admin tools and web sites which need to be be an admin to access certain things. readonly = Secret for authentication as 'readonly' user, which can't do too much but read the motd and some other things. host_foo = Admin secret of UMLd running on host 'foo' uml_foo = Admin secret of UMLd running on UML with the umid of 'foo' Both of the above are used for UMLd -> UMLd connections. > thanks for your help. No problem. I need to document this thing :-) David -- David Coulson http://davidcoulson.net/ d...@vi... http://journal.davidcoulson.net/ |