On 2013/9/27 11:57, Dhaval Giani wrote: >>>>> >>>>> Clearly this rule is invalid. So yes, I would expect cgrules to fail. >>>>> (What to do with all processes for all users). I think the behavior is >>>>> just fine. >>>>> >>>>> Dhaval >>>>> >>>>> >>>> yeah, but what do you think the different behaviour between >>>> the two similar rules? the '*#' is invalid because the '#' >>>> means a comment, right? >>>> >>> >>> The two rules are *not* similar. They have specific meanings. The # >>> means, everything following this character on this line is to be >>> ignored. Which leaves with just "*". This by itself is invalid,and >>> therefore the program returns an invalid rule. I am not sure why you >>> are confusing the two. >>> >> It's because in cgconfig.conf the '#' means a comment just when it's in the >> starting of a line. So I just think the two configs(cgconfig.conf and >> cgrules.conf) >> should have the same behaviour. As mentioned above, maybe they are different. >> > > Ah, now I get your question. I don't have any strong feelings, but I > think most people are used to how it works. They are two different > programs, and have completely different parsing methods. So I think it > is fine as it is. I have certainly not heard of any usability > complaints till now. Do you think it is a major issue? > It's not a major issue.
Thanks! > Thanks! > Dhaval > > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel
