On Tue, 25 Sep 2007 16:19:18 +0530 Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx> wrote: > Hi, Kamezawa-San, > Hi, > Your changes make sense, but not CLUI (Command Line Usage) sense. > 1. The problem is that when we mix strings with numbers, tools that > parse/use get confused and complicated yes, maybe. > 2. ULONGLONG_MAX is a real limit, there is no such thing as unlimited. > If the user does ever go beyond ULONGLONG_MAX, we will limit him :-) > Oh. res_counter.c uses LONGLONG_MAX as default value. need fix ? or intended ? And okay there is no "unlimited" state. > Having said that, I do wish to have a more intuitive interface for > users. May be a perl/python script to hide away the numbers game > from the users. What do you think? > I agree with you that perl/python script can hide details. but they need knowledge about the maximum value, which is given as default value. In short, what I want is some value like RLIM_INFINITY in ulimit. Because it seems that res_counter.c will be used for other resouce control purpose, I thought some generic way (value) to know/specify "the maximum value" is helpful for all resource controller interface. If there is an concensus that treaing ULONGLONG_MAX as default, it's ok. Thanks, -Kame _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
