similar to: mbox File too large error

Hello, About the INBOX location when using maildir, in the wiki, http://wiki.dovecot.org/MailboxFormat/Maildir, I can read: " Directory Structure ~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain the messages for INBOX. The tmp directory is used during delivery, new messages arrive in new and read shall be moved to cur by the clients. " But in my Maildir, I see

Hello, On my home server (Debian etch, custom 2.6.28.2 kernel), I am using ext3 for both root and /home filesystems, with barriers enabled to prevent corruption caused by my PATA disk write cache. Looking for a better performance, I have also set the commit=nr option as described in linux-2.6.28.2/Documentation/filesystems/ext3.txt, so that I now have: niko at petole:~$ mount -t ext3

Hi all, I plan to run a dovecot IMAPS and POPS service on our network. We handle about 3 000 mailboxes. I thought first buying a topnotch server (8 cores and 16 Go RAM) with equalogic iSCSI SAN SAS 15K for storage backend. On second though (and after a comprhensive read of dovecot features), I saw in http://wiki.dovecot.org/MailLocation that index files can be created on a separete local

Hi, I am using dovecot on debian, with version 1.0.rc15-2etch4. Along with postfix. The deliver binary cannot deliver to large mailboxes. I cannot state an exact size limit but mbox mailboxes above 1GB seem to be affected. I have these in in postfix/main.cf mailbox_command = /usr/lib/dovecot/deliver mailbox_size_limit = 5120000000 The user.log file shows these (I believe if no logging is

On Mon, Oct 22, 2012 at 9:33 PM, Niko Zarzani <koni10 at hotmail.it> wrote: > Thank you, it was what I really was searching for :) > > However, I don't know if I well understood. I've find this link in the > second link which seemed what i was looking for: > http://nondot.org/sabre/LLVMNotes/BuiltinUnreachable.txt . > If I put around the code block (inside my

Thank you, it was what I really was searching for :) However, I don't know if I well understood. I've find this link in the second link which seemed what i was looking for: http://nondot.org/sabre/LLVMNotes/BuiltinUnreachable.txt .If I put around the code block (inside my function with precondition (x>0 && y>0)) a contruct like that that use __builtin_unreachable: int foo(int

Hi Niko, Do you mean branch prediction, i.e. __builtin_expect [1]? Many compilers support it, I think clang (LLVM's C/C++ frontend) is among them. - D. [1] http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html 2012/10/23 Niko Zarzani <koni10 at hotmail.it>: > Hi all, > Is there any way to tell LLVM some additional information about the > variables in the code in order to

I tried it on a simple file test.c (as you did) but actually clang does not show me any output. In addition I tried to set the CFLAGS specifying the -mllvm -time-passes options. However I still have anything about the time passes informations in the output and I also get this warning during the build with make:clang: warning: argument unused during compilation: '-mllvm -time-passes'Maybe

You may want to check this out: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-October/053924.html and also http://llvm.org/PR810 - xi On 10/22/12 6:05 PM, Niko Zarzani wrote: > Hi all, > Is there any way to tell LLVM some additional information about the > variables in the code in order to make better optimization? > For example, if my function has a certain precondition (such

To use options like "-time-passes" and "-stats" you need to prefix them with "-mllvm": clang -mllvm -time-passes -O3 test.c -o /dev/null Note that I believe you need asserts enabled or some other build configuration for this to work, the timing code is disabled in fully release builds IIRC. Hope this helps! ~Will On Thu, Sep 12, 2013 at 11:50 AM, Niko Zarzani

Hello, I read in the wiki (http://wiki.dovecot.org/MailboxFormat/mbox) about "From Escaping": "Dovecot doesn't currently do this escaping however. Instead it prevents this confusion by adding Content-Length headers so it knows later where the next message begins. Dovecot doesn't either remove the '>' characters before sending the data to clients. Both of these

On 14.01.2018 09:11, Thomas Manninger wrote: > Hi, > > i am using dovecot 2.2.33.2 on CentOS 7.4. > > Since i upgraded from CentOS 7.2. to CentOS 7.4. (without upgrading dovecot), my dovecot sieve-pipe scripts crash with Out of memory: > Out of memory (allocated 262144) (tried to allocate 8793 bytes) > > There are some memory limits in dovecot or sieve? Can i change

Hi all,Is there any way to tell LLVM some additional information about the variables in the code in order to make better optimization?For example, if my function has a certain precondition (such as x>0) then it will be possible to better optimize the code given that information (which the compiler does not know).I am new in this field and I don't know if there are ways to tell the compiler

Hi Limits: Where all working fine: core file size????????? (blocks, -c) 0 data seg size?????????? (kbytes, -d) unlimited scheduling priority???????????? (-e) 0 file size?????????????? (blocks, -f) unlimited pending signals???????????????? (-i) 257970 max locked memory?????? (kbytes, -l) 64 max memory size???????? (kbytes, -m) unlimited open files????????????????????? (-n) 65536 pipe

This compiler does not have mem-SSA, as far as I know, only few pass can propagate value along memory. You need to promote those local variable into register first before sccp is invoked. e.g1. opt a.ll -basicaa -gvn -sccp -S eg.2. opt a.ll -sroa -sccp -S On 4/16/13 12:37 PM, Niko Zarzani wrote: > Hi all, > > I am trying to see how single llvm optimizations work by running them

Hi, i am using dovecot 2.2.33.2 on CentOS 7.4. Since i upgraded from CentOS 7.2. to CentOS 7.4. (without upgrading dovecot), my dovecot sieve-pipe scripts crash with Out of memory: Out of memory (allocated 262144) (tried to allocate 8793 bytes) There are some memory limits in dovecot or sieve? Can i change this value? Kernel limitks: [root at xxx software]# ulimit -a core file size

Hi, perhaps this? > with new debian9: > open files (-n) 1024 Regards Urban Am 16.09.20 um 12:57 schrieb Maciej Milaszewski: > Hi > Limits: > > Where all working fine: > > core file size????????? (blocks, -c) 0 > data seg size?????????? (kbytes, -d) unlimited > scheduling priority???????????? (-e) 0 > file size?????????????? (blocks,

Hi! I have problem making ext3 FS on new disk. When I run mke2fs, it stops and gives me: "File size limit exceeded". Is this known issue? I'm running linux-2.4.10 with ext3 patch, e2fsprogs-1.25 freshly compiled. Cheers, Vita Appended are outputs of following programs: bash /usr/src/linux/scripts/ver_linux /sbin/mke2fs -m0 -v -j /dev/sdb1 fdisk -l /dev/sdb strace

Hi all, I was interested in knowing which of the passes spends the most of the time compiling the dns server BIND.With the -CC option I selected clang as my compiler and, as I was expecting, the compilation gave me no problems.Now I have a question, is there any way to set an option similiar to "-time-passes" to clang in order to get those information I was interested in?Or do you think