Date: Tue, 12 Jul 2005 16:03:34 +0300 From: Vlad GALU <vladgalu@gmail.com> To: Jone Jas <jas_arlerr@yahoo.com.cn>, freebsd-hackers@freebsd.org Subject: Re: limit jail disk space Message-ID: <79722fad0507120603528ab24c@mail.gmail.com> In-Reply-To: <20050712121230.16762.qmail@web15010.mail.cnb.yahoo.com> References: <200507121114.42653.dom@goodforbusiness.co.uk> <20050712121230.16762.qmail@web15010.mail.cnb.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/12/05, Jone Jas <jas_arlerr@yahoo.com.cn> wrote: > Thanks for your reply. I googled and found this method but I just > did not have a try. > As for the code-hacking method I mentioned, anyone with any idea > is appreciated! <snip> =20 See ufs_quota.c, especially chkdqchg(). It is passed a struct ucred* parameter, which contains a struct prison* pointer. So I assume you can make your decision based on that. Of course, the userland quota management tools and the jail utilities need to be made aware of the kernel changes. --=20 If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79722fad0507120603528ab24c>