dovecot-1.1: If writing to log failed with EAGAIN (shouldn't nor...
dovecot at dovecot.org
dovecot at dovecot.org
Sat Jun 7 05:10:31 EEST 2008
details: http://hg.dovecot.org/dovecot-1.1/rev/7c9895192a23
changeset: 7615:7c9895192a23
user: Timo Sirainen <tss at iki.fi>
date: Sat Jun 07 05:10:26 2008 +0300
description:
If writing to log failed with EAGAIN (shouldn't normally happen), waiting
for the log fd to be writable again was buggy.
diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
src/lib/failures.c | 2 +-
diffs (12 lines):
diff -r dd899a1841d9 -r 7c9895192a23 src/lib/failures.c
--- a/src/lib/failures.c Fri Jun 06 20:08:23 2008 +0300
+++ b/src/lib/failures.c Sat Jun 07 05:10:26 2008 +0300
@@ -98,7 +98,7 @@ static int log_fd_write(int fd, const un
/* wait until we can write more. this can happen at least
when writing to terminal, even if fd is blocking. */
ioloop = io_loop_create();
- io = io_add(IO_WRITE, fd, log_fd_flush_stop, ioloop);
+ io = io_add(fd, IO_WRITE, log_fd_flush_stop, ioloop);
io_loop_run(ioloop);
io_remove(&io);
io_loop_destroy(&ioloop);
More information about the dovecot-cvs
mailing list