On Wed, October 11, 2023 10:44 pm, Matus UHLAR - fantomas wrote: > On 11.10.23 22:21, li...@sbt.net.au wrote:
> Here is your 5-minute delay. It's possible that scanning took too much of > time. Perhaps too many concurrent amavis sessions? from htop , by CPU % PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 22097 amavis 20 0 392M 70084 5676 R 100. 1.8 0:27.24 /usr/sbin/amavisd (virgin child) 8675 amavis 20 0 403M 97980 6264 S 0.0 2.5 9:59.10 /usr/sbin/amavisd (ch11-avail) 17438 amavis 20 0 386M 37200 664 S 0.0 1.0 0:08.36 /usr/sbin/amavisd (master) 24018 amavis 20 0 1833M 1320M 1392 S 0.0 34.8 0:00.87 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf 24003 amavis 20 0 1833M 1320M 1392 S 0.0 34.8 25:32.45 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf 22250 amavis 20 0 1833M 1320M 1392 S 0.0 34.8 0:00.20 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf 22251 amavis 20 0 1833M 1320M 1392 S 0.0 34.8 0:00.11 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf as I'm watching, the very first line seems stuck at first line position, others come and go Voytek
