> chroot builders do call ~= `sudo chroot` at some point.
The main work is done by sbuild, which uses schroot, not "sudo chroot".
(We used to use sbuild's sudo session mode, but I changed that to
schroot in 2017.)
> would changing limits.d + adding pam_limits to sudo pam config be
> enough for launchpad-buildd?
I think schroot does support PAM. However, I don't think it's good
design for launchpad-buildd to rely on PAM, since after all it's not
doing any kind of interactive authentication. I would rather not pursue
this option any further. There are other less complicated ways to set
resource limits.
--
Colin Watson (he/him) [cjwatson@canonical.com]
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
