Please reopen, at least while discussing with upstream. The bug is, that the current default value creates a dependency to the pam configuration where installing only a single debian packages (libpam_smb) makes dovecot fail.
Whereas the documentation says "This is mainly intended to catch and kill processes that leak memory before they eat up everything." So now the to small default values makes everything eaten up, instead of protecting against, which has been intended. Additionally, not fixing this requires the decision of some debian council, as it renders debian incompatible with itself. Am 06.02.2017 um 20:38 schrieb Apollon Oikonomopoulos: > Control: retitle -1 dovecot-core: default vsz_limit may cause PAM > authentication failures > Control: tags -1 - moreinfo unreproducible + wontfix > > On 20:31 Mon 06 Feb , Herbert Schmid wrote: >> I tried various values for default_vsz_limit. >> It failes with 256M and 258M, but succeedes with 260M and above. >> >> 256M seem to be reasonable value for 32-Bit-Systems, but with >> 64-bit-opcodes libraries are to big. >> >> pam_smb loads a lot of libraries, so it takes much memory. But there is >> at least one more pam module i like to use addionally to pam_smb. so the >> default value should be greater than the 260M from above. >> >> A reasonable default value would be 384M or 512M (on 64-Bit-Systems), or >> the like. > > Well, it depends on your PAM configuration really. On my production > servers, auth processes are < 128M in vsize. I'm a bit relucant to > change the default, we can discuss it with upstream first. > >> Thanks for the help, I now know which knob to use to make thinks work. > > Thanks for helping to pinpoint the exact cause. Most likely this is also > what the original submitter saw. > > I'm marking it as wontfix for the time being, but leaving it open for > documentation purposes. > > Thanks, > Apollon >
