oiaohm wrote: > http://lwn.net/Articles/268937/ << Hopefully Ubuntu build with cgroup in kernel. Thinking in newer Linux kernel you have to go out of your way to disable it. When building kernel from source graphical configuration don't even give you the option to disable it. Since its classed as kinda key feature. > > Cgroups can do a lot more than just memory control they can also control what devices a application can access, network access what percentage and ammount of cpu time applications get. Really useful tool for misbehaving programs. > > Thing most people are not aware is that all processes in kernels with cgroups enabled are always running in a cgroup. The default cgroup. Any process that a application starts remains in the cgroup the application that started it is in unless assigned else where. > > Becareful with them very powerful tool. Highly useful. Controlling cgroups is one time where running as root/admin is kinda required. Knowing the process id of a normal users shell allows that to be transfered into cgroup to run wine. echo $$ will tell you the PID of current bash. When you suggested using cgroups as a workaround, were you referring to these bugs? : http://bugs.winehq.org/show_bug.cgi?id=13335 http://bugs.winehq.org/show_bug.cgi?id=10778 Because I tried it, but could only get to it to limit RSS memory (which doens't solve the problem) not VIRT memory, which still grows to 4096mb and greater, even with much lower RSS limits (I tried down to 512MB)
