You need to include master-service.h to get master_service_get_process_limit,
which returns how many processes of this type can be created before reaching
the limit.
vsz_limit includes mmap and malloc allocations. dovecot uses setrlimit() to
enforce the memory limit, so getrusage() should give
Looking forward to any help
On Tue, 2024-10-08 at 08:45 +0800, Joan Moreau via dovecot wrote:
> Additionally, I get error:
> 'master_service_get_process_limit' was not declared in this scope
> (dovecot git version)
>
> On Tue, 2024-10-08 at 08:16 +0800, Joan Moreau via dovecot wrote:
> > Hi
>
Additionally, I get error:
'master_service_get_process_limit' was not declared in this scope
(dovecot git version)
On Tue, 2024-10-08 at 08:16 +0800, Joan Moreau via dovecot wrote:
> Hi
>
> What is the link between getrlimit (linux posix) , the vsz_limit
> parameter nd " MemAvailable" from /
Hi
What is the link between getrlimit (linux posix) , the vsz_limit
parameter nd " MemAvailable" from /proc/meminfo ?
Is there a way to see how much of the allocated memory (vsz ?) the
process is using in dovecot ?
Does that vsz limit take into account the direct malloc ?
For the master_
Hi
What is the link between getrlimit (linux posix) , the vsz_limit
parameter nd " MemAvailable" from /proc/meminfo ?
Is tehre a way to see how much of the allocated memory (vsz ?) the
process is using in dovecot ?
Does that vsz limit take into account the direct malloc ?
Thankyou
On 20
With 2.3 you can use master_service_get_process_limit() for the process limit.
To get vsz_limit, it's probably easiest to use getrlimit().
Aki
> On 07/10/2024 19:00 EEST Joan Moreau via dovecot wrote:
>
>
> get_rusage does not give me the value of vsz_limit from dovecot.conf !
>
> Need also
get_rusage does not give me the value of vsz_limit from dovecot.conf !
Need also process_limit (also from dovecot.conf)
Thank you
On 2024-10-07 14:13, Aki Tuomi via dovecot wrote:
On 07/10/2024 07:36 EEST Joan Moreau via dovecot
wrote:
Hi
How to get (programatically, c++) the current usag
> On 07/10/2024 07:36 EEST Joan Moreau via dovecot wrote:
>
>
> Hi
>
> How to get (programatically, c++) the current usage of memory, under the
> limit of vsz_limit ?
>
> https://doc.dovecot.org/2.3/configuration_manual/service_configuration/#service-configuration-vsz-limit
>
> Thank you
SOrry, my mistake, the conversion type was wrong.
So restrict_get_process_size is indeed consistent with vsz_limit
Now, for the memory usage of the process, getrusage gives only the /max/
of the memory used, not the current
THe only way I found is to fopen("/proc/self/status") and read the
c
ok found it,
However, it returns me some random number. Maybe I am missing something
On 2020-11-06 13:57, Aki Tuomi wrote:
Duh... src/lib/restrict-process-size.h
Should be in the installed include files as well,
/usr/include/dovecot/restrict-process-size.h
Aki
On 06/11/2020 15:56 Joan More
Hello
I can't find "src/lib/restrict.h" . Is it in dovecot source ?
On 2020-11-06 13:20, Aki Tuomi wrote:
Seems I had forgotten that you can use src/lib/restrict.h, in
particular, restrict_get_process_size() to figure out the limit. You
can combine this with getrusage to find out current usag
yes, will do so.
It would be nice however to be able to access the actual dovecot config
from the plugin side
On 2020-11-04 06:46, Aki Tuomi wrote:
You could also add it as setting for the fts_xapian plugin parameters?
Aki
On 04/11/2020 08:42 Joan Moreau wrote:
For machines with low memo
Duh... src/lib/restrict-process-size.h
Should be in the installed include files as well,
/usr/include/dovecot/restrict-process-size.h
Aki
> On 06/11/2020 15:56 Joan Moreau wrote:
>
>
> Hello
> I can't find "src/lib/restrict.h" . Is it in dovecot source ?
>
>
> On 2020-11-06 13:20, Aki Tuom
Seems I had forgotten that you can use src/lib/restrict.h, in particular,
restrict_get_process_size() to figure out the limit. You can combine this with
getrusage to find out current usage.
Aki
> On 06/11/2020 13:26 Joan Moreau wrote:
>
>
> yes, will do so.
> It would be nice however to be a
For machines with low memory, I would like to detect how much ram
remains available before starting indexing a mail, so I can commit
everything on disk before the ram is exhausted (and break the process)
I tried to put a "fake" allocation to test if it fails, (so it can fail
separately, and I
You could also add it as setting for the fts_xapian plugin parameters?
Aki
> On 04/11/2020 08:42 Joan Moreau wrote:
>
>
> For machines with low memory, I would like to detect how much ram remains
> available before starting indexing a mail, so I can commit everything on disk
> before the ra
> On 04/11/2020 05:19 Joan Moreau wrote:
>
>
> Hello
> I am looking for help around memory management
> 1 - How to get the current value of "vsz_limit" from inside a plugin (namely
> https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker
> 2 - Is there a macro or function in
> On 04/11/2020 05:19 Joan Moreau wrote:
>
>
> Hello
> I am looking for help around memory management
> 1 - How to get the current value of "vsz_limit" from inside a plugin (namely
> https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker
> 2 - Is there a macro or function in
On Sep 15, 2014, at 10:20 AM, Dan Langille wrote:
>
> On Sep 8, 2014, at 6:38 PM, Jiri Bourek wrote:
>
> Background: I’m in the only user on this system, but this server is
> accessed by my phone, my laptop, my tablet, and perhaps a web interface.
>
>
> But
On Sep 8, 2014, at 6:38 PM, Jiri Bourek wrote:
>>>
Background: I’m in the only user on this system, but this server is
accessed by my phone, my laptop, my tablet, and perhaps a web interface.
>>>
But there are some interesting values when I look at the output of
>>
On Tue, 9 Sep 2014, dovecot-requ...@dovecot.org wrote:
vsz_limit = 18446744073709551615 B
}
Still the same value? why not 265MB?
I guess this is Dovecot's approximation of infinity. It's the largest value
that fits into a 64-bit signed integer (2^64-1).
Joseph Tam
On Mon, Sep 08, 2014 at 04:41:18PM -0700, Robert L Mathews wrote:
> On 9/8/14 3:38 PM, Jiri Bourek wrote:> Hm, I can only guess (someone
> with more knowledge of dovecot source code
> > probably knows better), but it seems like that value is magic number for
> > "not set". My doveconf outputs the s
On 9/8/14 3:38 PM, Jiri Bourek wrote:> Hm, I can only guess (someone
with more knowledge of dovecot source code
> probably knows better), but it seems like that value is magic number for
> "not set". My doveconf outputs the same thing on services which don't
> have vsz_limit set explicitly, but whe
Background: I’m in the only user on this system, but this server is accessed by
my phone, my laptop, my tablet, and perhaps a web interface.
But there are some interesting values when I look at the output of doveconf.
Specifically, vsz_limit is 18,447 PB… yeah, that’s pretty big.
servic
On Sep 7, 2014, at 4:39 AM, Jiri Bourek wrote:
> On 6.9.2014 22:38, Dan Langille wrote:
>> I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3
>>
>> Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions
>> for change?
>>
>> Sep 6 03:39:32 mailjail dovecot: imap
On 6.9.2014 22:38, Dan Langille wrote:
I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3
Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for
change?
Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556
(imap_fetch_more): assert
26 matches
Mail list logo
