Re: [binc] NOOP fails (from time to time)

Peter Stuge <[email protected]>
Newsgroups gmane.mail.imap.binc.general
Message-ID <[email protected]>
On Fri, May 20, 2005 at 11:06:59AM +0200, J. Kendzorra wrote:
> strace says: 
> 
> ,---
> | write(6, "533 NOOP\r\n", 10) = 10
> | --- SIGCHLD (Child exited) ---
> | select(8, [0 7], NULL, NULL, {2160, 0}) = 1 (in [7], left {2160, 0})
> | read(7, "* BYE Invalid Mailbox, /new/: No"..., 8192) = 57
> | alarm(1200)                             = 0
> | write(1, "\27\3\1\0I\216\362(\320\377&\5\370\20F\256\347\366X\363"..., 
> 78) =
> | 78
> | alarm(0)                                = 1200
> | select(8, [0 7], NULL, NULL, {2160, 0}) = 1 (in [7], left {2160, 0})
> | read(7, "", 8192)                       = 0
> | close(7)                                = 0
> | close(6)                                = 0
> | wait4(14888, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 14888
> | alarm(1200)                             = 0
> | write(2, "14879 1 [[email protected]:]"..., 86) = 86
> | alarm(0)                                = 1200
> | munmap(0x28978000, 4096)                = 0
> | _exit(0)
> `--- 

Unfortunately this strace output isn't useful. This is the strace of
either tcpserver or bincimap-up and we need the strace from
bincimapd.


> It seems Binc is missing the path in "path + /new/"
> (maildir-scan.cc) after some time.

Hm, I'll go have a look at the code..


On Sat, May 21, 2005 at 06:47:41PM +0000, Casey Allen Shobe wrote:
> This is exactly the same problem that I've been experiencing, which
> causes mail clients to do "fun" things!  Woo hoo, glad I'm not the
> only person experiencing it (now to convince Andreas to fix it,
> which is another matter entirely ;-P ).

I'm sure Andreas will give due attention to a bug such as this, but
at the same time it would help if we could reproduce it or get more
info, I've been banging my 1.2.12final with NOOPs for a while now and
still no problem. :\


//Peter
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.