search for: timeout_add

...9, at 6.44, Tijl <dovecot at odie.be> wrote: > >> How can dovecot be run without writing to /var/lib/dovecot/instances everyday? Is there a configuration setting for this? > > You'd need to patch src/master/main.c instance_update_now() to remove: > > to_instance = timeout_add((3600 * 12 + i_rand_limit(60 * 30)) * 1000, > instance_update_now, list); > > I'm not quite sure why I wrote such code to update it continuously. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/201...

...3317538000, u64=94320799358160}}) = 0 09:27:52.838035 epoll_ctl(14, EPOLL_CTL_DEL, 213, 0x7ffe8e642cdc) = 0 09:27:52.838070 epoll_ctl(14, EPOLL_CTL_ADD, 213, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP, {u32=3317538000, u64=94320799358160}}) = 0 "ltrace" showed the same loop as: 10:38:01.773867 timeout_add(0x7530, 0x55c8c351df75, 965, 0x55c8c3515a00) = 0x55c8c5c658b0 10:38:01.774060 timeout_remove(0x55c8c5acf7a8, 0, 0xffffffff, 0) = 0 10:38:01.774239 io_add(213, 1, 0x55c8c351df75, 1070) = 0x55c8c5c658b0 10:38:01.774429 io_set_pending(0x55c8c5c658b0, 1, 0x55c8c54b8aa0, 0x7fb4ab11b06a) = 0x55c8...

In my development environment I sometimes get: dovecot: IMAP(stava): Timeout leak: 0x4425d0 Does anyone know what it means or how I can use this information? Cheers /Lars

Hi, I hope someone can help me with this. Problem Dovecot writes to _/var/lib/dovecot/instances_ 1 up to 3 times a day, causing the system to wake up and disks to spin up. Details content of /var/lib/dovecot/instances : 1549073010 dovecot /var/run/dovecot /etc/dovecot/dovecot.conf --> only the timestamp is changed (to current time) when dovecot writes to this file --> during write the

...= (struct mail_storage *) 0xb7c08 real_mailbox = 0xb8128 "mail/AutoFiled/2006" str = (string_t *) 0x10 #11 0x0002287c in client_handle_input (cmd=0xb7dd0) at client.c:380 client = (struct client *) 0x210e8 __PRETTY_FUNCTION__ = "parameter \0\0\0\0\0\0Inva" #12 0x0007e3bc in timeout_add (msecs=743112, callback=0xab800, context=0xac400) at ioloop.c:152 timeout = (struct timeout *) 0x2 #13 0x0007dcb4 in _seek (stream=0xb56c8, v_offset=3039960672808960, mark=116) at istream-mmap.c:149 No locals. #14 0x0002ab24 in main (argc=-4195379, argv=0xab800, envp=0xac400) at main.c...

On 2 Feb 2019, at 6.44, Tijl <dovecot at odie.be> wrote: > How can dovecot be run without writing to /var/lib/dovecot/instances everyday? Is there a configuration setting for this? You'd need to patch src/master/main.c instance_update_now() to remove: to_instance = timeout_add((3600 * 12 + i_rand_limit(60 * 30)) * 1000, instance_update_now, list); I'm not quite sure why I wrote such code to update it continuously. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20190207/9b13...

...cot be run without writing to /var/lib/dovecot/instances everyday? Is there a configuration setting for this? Postfix can do this without that added infrastructure. > > > > You'd need to patch src/master/main.c instance_update_now() to remove: > > > > to_instance = timeout_add((3600 * 12 + i_rand_limit(60 * 30)) * 1000, > > instance_update_now, list); > > > > I'm not quite sure why I wrote such code to update it continuously. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions i...

mail1 dovecot: imap(smith at willcapmanagement.com): Timeout leak: 0x807fad0 Can anyone give me a heads up on what might cause the above message? I am working on polishing a plugin and it continues to throw this error with no seeming consequences. -David

...t;io) { + old.io = *pgc->io; + io_remove(&pgc->io); + + pgc->io = io_add(PQsocket(pgc->pgc), + old.io.condition, old.io.callback, old.io.context); + } + + if (pgc->timeout) { + old.timeout = *pgc->timeout; + timeout_remove(&pgc->timeout); + + pgc->timeout = timeout_add(old.timeout.msecs, + old.timeout.callback, old.timeout.context); + } +} + +static void log_pg_error(struct multi_pgsql_pgc *pgc, char const *fnc, char const *pg_call) +{ + i_error("%s: %p: %s: %s", + fnc, pgc, pg_call, kill_pg_errmsg_newline(PQerrorMessage(pgc->pgc))); +} + +/*...

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. Native Push Email has some great advantages: it speeds up email notifications (usually within seconds of being handled by dovecot-lda) and it improves battery life since

...ib/libc.so.1 > #3 0xff1c1dec in _malloc_unlocked () from /usr/lib/libc.so.1 > #4 0xff1c1ce0 in malloc () from /usr/lib/libc.so.1 > #5 0xff1b617c in calloc () from /usr/lib/libc.so.1 > #6 0x89c18 in pool_system_malloc (pool=0xb66f0, size=28) at mempool-system.c:67 > #7 0x86d7c in timeout_add (msecs=1740000, callback=0x1f920 <idle_timeout>, context=0xc4a18) at ioloop.c:146 > #8 0x1fda0 in cmd_idle (cmd=0xc27a4) at cmd-idle.c:245 > #9 0x23334 in client_handle_input (cmd=0xc27a4) at client.c:331 > #10 0x232b4 in client_handle_input (cmd=0xc27a4) at client.c:388 > #11 0...

This introduces support to run P2V without X server. Runtime parameters are specified via kernel command line making it hopefully suitable for automated migration with a little help of PXE boot. Patchset is not squashed and represents dev. history.

I hacked some command line options into imaptest. I dont think I broke it.. Place into dovecot-source root as usual and compile with: gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H src/lib/liblib.a As per Timo's instructions. # imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX] [clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO] USER = template for