Roger Leigh <rle...@codelibre.net> writes: > > The PAM auth and session handling is I think the most likely culprit, > and this is not under our direct control. Is there a particular PAM > module which can change these cpusets? If so, can you edit the > schroot PAM configuration and see if it can be disabled this way? > Possibly in @common-session?
I'm not sure (yet) what if any pam module resets the Cpu_allowed mask, but your idea seems worth investigating to me, since I noticed the same behaviour with su. d
