similar to: time out error and email with attachments

Dear all, I'm using a binomial distribution with a logit link function to fit a GAM model. I have 2 questions about it. First i am not sure if i've chosen the most adequate distribution. I don't have presence/absence data (0/1) but I do have a rate which values vary between 0 and 1. This means the response variable is continuous even if within a limited interval. Should i use

Timo, I upgraded from alpha3 to alpha4 yesterday, and I am seeing a few of the following asserts: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) Gdb info on a couple of the cores is attached. It looks like the arg lock_type for mbox_lock_fcntl() is not getting passed in correctly, like the enum "enum mbox_lock_type type" in

I can't download my email if the email has one attachment. It goes in time out. This is the log: (how to verbose more information in dovecot.log?) version: fedora core 4 and dovecot 0.99-14-4 Can anyone tell me if this can be the problem to not able to retrieve the email from dovecot? ==> /etc/dovecot.log <== dovecot-auth: Sep 28 17:37:03 Info: Login process 8 disconnected

I am running Fedora 8 uname -r = 2.6.24.4-64.fc8 on my box with Wine 0.9.58. When I first installed it I noticed that my CPU usage jumped and stayed at 100% with wineserver taking > 85%. I killed the wineserver process and it dropped down, however it soon jumped back up when wineserver restarted itself. I then killed it again and all related processes and disabled it from starting as a damen

Hi Benjamin: I think that the following link will give you an idea for what you need to know: http://www.cisco.com/warp/customer/620/roadmap_b.shtml This is for the naming: http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_tech_note09186a0080101cda.shtml In this case 11.1CC goes to 12.0T and 12.0T migrate to 12.1 mainline. Do not you worry you will not loose anything with the new

Hello, > I upgraded from alpha3 to alpha4 yesterday, and I am seeing > a few of the following asserts: > > imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): > assertion failed: (lock_type == F_UNLCK) I'm getting this error too after upgrading to alpha4. > Gdb info on a couple of the cores is attached. It looks > like the arg lock_type for mbox_lock_fcntl()

Timo, I have had to drop back to alpha3 because I found a pile of core files on my imap server this morning, from the weekend. They are all from the assert: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) I reported this issue to the list last Friday. Help... Jeff Earickson Colby College

Hi, So I've been through google and the dovecot source and have not yet found a reasonable explanation for the 'Timeout while waiting for lock' error. My customer's configuration is utilizes mbox with the following mbox configs. [snip] pop3_lock_session = yes mbox_read_locks = fcntl mbox_write_locks = fcntl mbox_lock_timeout = 300 [/snip] I see from the source that this error

Hi, When the Dovecot 1.0.rc19 IMAP server encounters X-UID headers with gaps in them, it hangs indefinitely. I've attached a sample mailbox (in mbox format) which repeatably exhibits this behavior. The mbox contains only three messages with the following X-UIDs in order: 774, 785, 787. If I remove the X-UID headers from each message, Dovecot handles the mailbox without any problems. UW-IMAP