search for: iolooping

Hello, ioloop->highest_fd is used by ioloop-select.c only, so its handling can be moved out of generic ioloop code. Attached patch (agains -test35) does exactly this. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -urpNX /usr/share/dontdiff -x Makefile

Hi, I would like to submit the attached patch. It implements IO loop using FreeBSD's kqueue/kevent syscalls. It is based on snapshot of CVS HEAD as of 2005-12-12. I could only give it limited testing on FreeBSD 5.4 but it works fine so far. Vaclav Haisman -------------- next part -------------- diff -rN -u old-dovecot-cvs/autogen.sh new-dovecot-cvs/autogen.sh ---

Hello, currently I'm working on new ioloop handler which uses epoll(4) API introduced in Linux kernel 2.6. In this API each fd added to fd set by epoll_ctl system call can be accompanied with user supplied data (integer or void pointer). epoll_wait syscall reports arrived events as an array of structures containing event mask and user data. Attached patch replaces fd and condition parameters

Hello, attached patch adds experimental ioloop handler which uses BSD kqueue API. It compiles and survives my small test program, but not thoroughly tested because I have no suitable BSD machine to torture. Brave owners of (Free|Net|Open)BSD please test and report results :) Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net

Sorry, I forgot to attach patch to previous mail. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -urpNX /usr/share/dontdiff dovecot-cvs.vanilla/configure.in dovecot-cvs/configure.in --- dovecot-cvs.vanilla/configure.in 2004-08-09 23:14:02.000000000 +0400 +++ dovecot-cvs/configure.in 2004-08-25

Hi, the attached patch contains these changes: 2005-12-15 22:18 Vaclav Haisman <v.haisman@sh.cvut.cz> * src/lib/ioloop-kqueue.c: Fix IO_ERROR behaviour. * src/lib/ioloop-notify-kqueue.c: New file. * configure.in: Improve kqueue detection and handling. Cleanup. The configure.in changes that are not related to kqueue are there to make autoconf 2.59, automake 1.9.6 and libtool 1.5.20

Hi, Can't find any notes about this in documentation. Is replication supposed to work between different versions of dovecot? I've just found that dovecot 2.2.33.1 was uploaded to debian unstable and it crashes on every replication with older dovecot 2.2.27. (version 2.2.32.1 was probably ok) Summary: - 2.2.33.1 crashes when replicating from/to 2.2.27 - 2.2.32.1 probably ok when

Hey, I noticed that there was an ioloop "module" (if we can call it that) for select and poll and decided to add one for kqueue (aka kevent) BSDs high performance descriptor multiplexing API. I haven't done any of the configure glue stuff but the code is complete and works well. kqueue is available on all recent versions of FreeBSD, NetBSD, OpenBSD and Darwin (and therefore MacOS

Hi there, I get a crash when doing "make check" for version 2.3.0 on Solaris Sparc. The build was done with gcc 7.3.0. The crash happens in ioloop-poll.c line 181 when running test_istream_multiplex.c: #0 io_loop_handler_run_internal (ioloop=ioloop at entry=0x130dd0) at ioloop-poll.c:181 181 if (pollfd->revents != 0) { Due to the code 180

Hi, since a couple of weeks I occasionally have an imapd going crazy on me, using up 100% CPU. Current revision is 10962 29865 vmail 20 0 47820 3296 1708 R 99.7 0.9 131:07.85 imap vmail 29865 86.1 0.8 47820 3296 ? R Mar20 131:20 dovecot/imap [berni 2001:a60:f001:1:219:66ff:fe8b:a6e IDLE strace -p <pid> shows a repeating pattern of epoll_wait(8, {{EPOLLOUT,

Howdy, Forgive me if this issue has been more recently addressed in CVS, but a quick scan of the archives didn't turn up any other reports. There appears to be a small typo in src/lib/ioloop-select.c: --- dovecot-1.0.alpha4/src/lib/ioloop-select.c.orig 2005-11-06 22:06:53.000000000 -0800 +++ dovecot-1.0.alpha4/src/lib/ioloop-select.c 2005-11-06 22:07:13.000000000 -0 800 @@ -113,7

Hi, I have one user constantly crashing with: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb) bt #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0,

Hi! This is a issue that has been fixed in master, thank you for reporting. See https://github.com/dovecot/core/commit/187fbf157d5c42f9f06ce52884fefbb4f66c070d.patch Aki On 17.10.2017 21:12, Dmitry Nezhevenko wrote: > Hi, > > Can't find any notes about this in documentation. Is replication supposed > to work between different versions of dovecot? > > I've just found

In data marted? 18 settembre 2018 14:07:26 CEST, Aki Tuomi ha scritto: > If you are using systemd, create > /etc/systemd/system/dovecot.service.d/limits.conf and put > [Service]LimitCORE=infinity > > and run > systemctl daemon-reloadsystemctl restart dovecot Nope, I'm on a debian 7, without systemd. Anyway, I've resolved the issue: I had to set fs.suid_dumpable BEFORE

I'm running Dovecot as proxy in front of some IMAP/POP3 Dovecot & Courier-IMAP servers and in the last couple of days I've been seeing a lot of imap-login crashes (signal 11) on both 2.2.18 and 2.2.25, all SSL related. The following backtraces are taken running 2.2.25, built from source on a test system similar to the live proxy servers. OS: CentOS 6.8 64bit Packages:

On 19.07.2017 09:39, Aki Tuomi wrote: > > On 19.07.2017 09:36, Thomas Leuxner wrote: >> * Aki Tuomi <aki.tuomi at dovecot.fi> 2017.07.19 08:31: >> >>> oh and any idea which one of these crashes? >> This one does: >> >> # cat Flagged/dovecot-virtual >> * >> :public/* >> -Trash >> -Trash/* >> flagged > Thanks,

When in the process of testing out the 2.3.0 version of Dovecot, we noticed that on a busy server, imap-login can sometimes take 100% CPU and remain there indefinitely. We grabbed a gdb trace while it was happening: dovenull 36053 31.2 0.0 60460 17316 ? R 04:38 11:55 dovecot/imap-login root at server [~]# strace -p 36053 Process 36053 attached ^CProcess 36053 detached root at server

Hello, coredump found after a force-resync and a replicate Emmanuel. (dovecot-ee 2.2.30.2-1) [New LWP 17168] Core was generated by `dovecot/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fa334127c37 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #0 0x00007fa334127c37 in __GI_raise (sig=sig at entry=6) at

#0 0x00007f497ecdb067 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 10092 selftid = 10092 #1 0x00007f497ecdc448 in __GI_abort () at abort.c:89 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0xfffe, sa_sigaction = 0xfffe}, sa_mask = {__val = {1024, 140722499998576, 94791001010256, 513,

* Thomas Leuxner <tlx at leuxner.net> 2017.07.19 14:29: It seems to have a new side effect which I haven't noticed upfront as it does not produce logging in Dovecot: Program terminated with signal SIGSEGV, Segmentation fault. #0 io_loop_extract_notify_fd (ioloop=0x563456973540) at ioloop-notify-inotify.c:224 224 ioloop-notify-inotify.c: No such file or directory. (gdb) bt full #0