On 14.03.24 21:21, Joan Moreau wrote:
I am trying to avoid closing/ reopening a file pointer to the exact same file
between each call to the plugin

That's still a "what" and not a "why". Long before you'll run into any serious resource problem, that file will be firmly seated in the disk cache and (r/o) accessing it will *effectively* be done in RAM; probably still not quite as efficient as Shared Memory, but.

I seriously doubt that the dovecot developers will want to make their software into the plugins' new memory manager, replacing the kernel in that role - having a plugin run amok and cause the master dovecot process to abort due to OOM sounds like creating an even worse problem, frankly ...

Kind regards,
--
Jochen Bern
Systemingenieur

Binect GmbH

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to