Am 20.10.2018 um 19:06 schrieb Wietse Venema: Hi,
>> If a client disconnects very early, the smtpd is still "unused" and >> remains in server memory, waiting for the next connection. > > The Postfix behavior has nothing to do with the duration of an SMTP > session. It is determined by the max_idle setting in main.cf. max_idle was the option I was looking for. Thank you. I always grepped for something like timeout/daemon/time and I never found max_idle. :-) > You would see the same with a sustained peak of one minute long. > It does not depend on the length of SMTP sessions. Yes and No. If a client connects to smtpd and then breaks the connection because there's only STARTTLS or AUTH ONLY we have those remaining smtpd processes -- which makes the server looking busy, while he isn't. If there's really a long peak then the server IS busy and I WANT to have an alarm. >> In that situations we're seeing false positives in our monitoring. > Please fix your monitoring! Yes, I do that -- that's why I'm requesting help (thanks for max_idle) or some additional changes to enable a better monitoring. > Conclusion: prctl(PR_SET_NAME) is safe to use. I would not > distribute Postfix's own version of the stinking pile of garbage > that mucks direclty with argv[]. :-) I don't understand much about the differences and the different way on how to implement that. -I'm not a coder, just an Admin. I only now that this way's working really perfect with Dovecot for me and it's very helpful to get an quick overview about what's going on and who is eating up your ressources. So if this could be implemented some day... I'd appreciate that. Peer
