[...] > Solaris Zones is not a realistic options, with some > 200-300 customers per server. (Solaris zones tend to > handle 5-10 per server before becoming unusable).
That would depend on memory (and core or thread count), I would think. ISTR reading about someone creating 100 or more zones on a pretty wimpy machine. Not that those zones were doing anything much beyond booting up. (However, patching can get quite cumbersome with a lot of zones.) Aside from having a bunch of processes associated with each running zone (which are taking of a fair bit of VM, mostly shared, and most of the time very little CPU), a zone is pretty much chroot on major steroids (insofar as it confines more than just the accessible path names, and adds per-zone resource controls). It's a lot lighter than a VM or LDOM. If you really wanto to play with chroot-ed environments, I think you're mostly on your own. You might want to explore using loopback mounts of /lib, /usr/lib, /usr/bin, and maybe one or two other carefully-chosen directories, with private copes of /etc and /var. But aside from those extra processes (and a per-zone IP address), that's not much less than what zones set up for you anyway. I think that probably if you can't re-think what you're doing so that you don't have to be using the same UID for different accounts, you'll probably find that zones are the simplest solution for you, even if it means you need a few more servers. -- This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list sysadmin-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
