Uhm. I do see the point. Virtual server webhosting. A decent way to limit their disk space consumption at the same time avoid waste of space. When a "simple" webhosting account can easily use up 500-1000MB of data which 90% is the same data across all servers. Unify to simplify updates and save space 10 vservers might save 9 gig of space easily.
However one thing I personally see as more important is the ability to restrict memory usage and cpu resource usage. Best regards, Eje Gustafsson mailto:[EMAIL PROTECTED] The Family Entertainment Network http://www.fament.com Phone : 620-231-7777 Fax : 620-231-4066 - Your Full Time Professionals - Mikrotik OEM dealer - Online Store http://www.fament.net/ -- JB> Herbert Poetzl wrote: >> To Potential Testers! >> >> updated the Context Quota Stuff to cq0.06 (and 2.4.22) >> and added a per context Disk Limit dl0.02 to enable >> virtual disk limits per context (per quota hash) ... JB> i'm not really sure i understand why you and others spend so much time JB> on the quota stuff. Because even if you install alot of services inside JB> a vserver, i doubt that you'll use more than a max a GB, and proberly JB> half. The stuff that takes up space is content, and that can NOT be JB> shared across vservers. (personaly i use one LV from the LVM system JB> for each vserver). JB> I would imagien that the stuff that limits how many vservers you can run JB> on a single system is memory, though perhaps the new 64bit computers JB> will change that, but then maybe cpu is the problem. How many vservers JB> can you run at a production system anyway? 10? 100? 1000? JB> JonB -- [This E-mail scanned for viruses by Declude Virus]
