Date: Fri, 05 Mar 2004 15:40:49 +0100 From: Eirik Oeverby <ltning-freebsd-current@anduin.net> To: Andy Hilker <ah@crypta.net> Cc: current@freebsd.org Subject: Re: Jails in -CURRENT Message-ID: <1078497649.98622.20.camel@eirik.unicore.no> In-Reply-To: <20040305143523.GA63132@mail.crypta.net> References: <20040304170746.GA4259@mobile.acs-et.com> <20040305131718.GC1458@lewiz.org><20040305140609.GD1458@lewiz.org> <20040305143523.GA63132@mail.crypta.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I've put up a webpage about my script and a download link. Have a look. Keep in mind that I have big plans for this, and progress is being made rapidly ;) http://anduin.net/?page=anduin&subpage=me&topic=jailctl /Eirik On Fri, 2004-03-05 at 15:35 +0100, Andy Hilker wrote: > > I have some pretty hefty jail configs too > > What about tools and management, what do you use? > Are you using real virtual systems with own filesystems or do you > mount from host system? > Do you have experiences with devfs rules? > Sorry if i asking too much, i am just curious :) > > > > me that if an ``exception'' (maybe it isn't even this?) is made, more > > might follow. > > Maybe no exception but a useful integration of a powerful jail > management... Main knobs in rc.conf, detailed config outsourced > (simple: see inetd.conf...) > > I am also wondering about a useful integration of jls and jexec. > In my scripts i use silly things like "grep all procs, see in /proc > which is running in this jail, kill it". > Very ineffecient, but effective. But jexec and jls are available > und useful now (btw. thanks!). > > Ok, i am curious what Mike Makonnen will do. > > I think, there is more documentation or hints needed. Many things > i have learned by using jails, but found it nowhere written down. > For example what to disable in rc.conf and cronjob "entropy". Entropy > makes heavy cpu load when running much jails. > And so on... > > Maybe someone could collect (i would do this) all experiences, tips, > hints, bugs, feature requests and so on. And then post and discuss > it here for next steps leading to more documentation and new tools.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1078497649.98622.20.camel>