ok but this does not consider the vsz_limit of the service (indexer in
my case)
only the "default_vzs_limit" is given
On 2021-11-21 13:14, Aki Tuomi wrote:
> Dovecot master process uses setrlimit to enforce the limit, so you
> should be able to get it with RLIMIT_AS or RLIMIT_DATA, iirc it depends
> a bit on os which is used.
>
> I dont think service->vsz_limit is available on the service itself.
>
> Aki
>
> On 21 November 2021 12.20.16 UTC, Joan Moreau <jom at grosjo.net>
wrote:
>
> In the dovecot source, I see "service->vsz_limit" giving the
answer
>
> How to reach the "service" object from within a plugin ?
>
> On 2021-11-21 12:15, Joan Moreau wrote:
>
> Hi
>
> This does not really work
>
> Putting
>
> service indexer-worker {
> vsz_limit = 1G
> }
>
> Getrlimit returns "-1"
>
> Is there a proper function giving the actual process size (memory
> used) and limit (vsz_limit, either process of default_vsz_limit, as
> applicable) ?
>
> On 2021-11-21 07:09, Aki Tuomi wrote:
>
> You could try getrlimit RLIMIT_AS.
>
> Aki
>
> On 20 November 2021 17.22.17 UTC, Joan Moreau <jom at grosjo.net>
wrote:
>
> Hello
>
> How to get, programatically (C/C++), the value of teh dovecot.conf file
> of vsz_limit and default_vsz_limit ?
>
> Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20211121/a1695a1c/attachment-0001.htm>