On 06/ 8/10 10:08 AM, Gordon Ross wrote: > I notice that onu runs pkg.depotd on the installing client, > accessing the bits over NFS. When clients are far from the > gate, or otherwise resource constrained (i.e. virtual), the > install process with onu can be slow and sometimes flaky. > > I'd like a configuration where pkg.depotd runs on the > machine hosting the project gate (similar to ipkg.sfbay) > but it's not clear how I set that up. Pointers? > > Thanks, > Gordon
Configure and enable the pkg/server service. I don't have a running example right now, so I might leave some info out, but this should get you started. The pkg.depotd(1M) manpage has useful information, and the README file for the repo-on-a-disk (http://nana.eng/products/solnext_dev/140/README.osol-repo) has some instructions. If you're not setting ON_CRYPTO_BINS in your project builds, then you'll need two instances of the pkg/server service: one for repo.redist and one fore repo.extra. You'll use svccfg to add instances, and each instance will need the pkg property group and some other properties. For example: svccfg -s pkg/server add myproj-redist svccfg -s pkg/server:myproj-redist addpg pkg application svccfg -s pkg/server:myproj-redist setprop pkg/port = 10000 I think you'll want to set the following: pkg/cfg_file Path to a persistent cfg_cache file. pkg/inst_root This should be a copy of repo.redist. pkg/port and possibly pkg/writable_root, if you don't want that data in inst_root. The pkg.depotd(1M) manpage has a complete list of properties. Similarly for on-extra. Then svccfg refresh pkg/server and svcadm enable your new instances. --Mark _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
