similar to: Locking foolishness

I realized that my last message about locking gave bad information -- or rather, very little information. Here's my setup: - Home directories and user login information are located on an Xserve running Mac OS X 10.2.6. Home directories are split between 2 different directories -- /Users and /Students. Home dirs are exported via NFS to the mail server. User login info is shared via LDAP

I have a really weird problem. To whit: I compiled dovecot 0.99.10 on two different systems: a linux-ppc box running Debian, and a Mac OS X Server v. 10.2.8. It compiled fine on both. The same Maildir's are being served up on both -- the OS X server exports home directories to the clients via NFS. BUT the OS X box orders mailboxes this way: INBOX Deleted Items Sent Items . . . And the

On 06/21/2010 08:21 PM, Eric Christopher wrote: > On Jun 21, 2010, at 2:56 AM, Patrick Marlier wrote: > > >> Hello, >> >> This bug affects all LLVM versions from 2.6 to trunk : >> http://llvm.org/bugs/show_bug.cgi?id=5081 >> >> The workaround I found is to add this : >> >> Index: lib/Target/X86/X86Instr64bit.td >>

hi all, i've just installed dovecot from debian sarge and i get this error: Jun 28 16:31:50 server pop3(user): file_wait_lock() failed with custom flags file /mnt/nfs/users/user//mail/.customflags: No locks available (maildir in nfs) how seriously i should take it ? is it fixed in newer versions ? thanks !

I'm getting this error for al my users does anybody know wat the problem is and how i can fix it pop3(bas at giskit.nl): Mar 06 09:10:37 Error: file_wait_lock() failed with index file /mailstore/vmail/giskit.nl/bas/.INBOX/.imap.index: No locks available Met vriendelijk groet, Bas van Dikkenberg GISkit bv BFVD1-RIPE Tel: +3130-6340430 Fax:

On 06/22/2010 11:11 AM, Patrick Marlier wrote: > On 06/21/2010 08:21 PM, Eric Christopher wrote: >> On Jun 21, 2010, at 2:56 AM, Patrick Marlier wrote: >> >> >>> Hello, >>> >>> This bug affects all LLVM versions from 2.6 to trunk : >>> http://llvm.org/bugs/show_bug.cgi?id=5081 >>> >>> The workaround I found is to

On Jul 7, 2010, at 4:52 AM, Patrick Marlier wrote: > Which one is correct ? > - movl $tm_nest_level at TPOFF, %ecx > or > - movq $tm_nest_level at TPOFF, %rcx > or > - movl tm_nest_level at TPOFF, %ecx > I believe this is initial exec and so from: http://people.redhat.com/drepper/tls.pdf it would be movl tm_nest_level at TPOFF, %ecx > Otherwise, Is there a

Hi, I am having problems with file locks with my NFS mounted Maildir setup. NFS Client/IMAP Server is RHEL3 clone whitebox and NFS server is a Fedora Core 2 system. Both are running lockd as far as I can tell. dovecot is installed with Dag's latest dovecot RPMs for RHEL3. Time is synced between the two systems. Here is the pertinent log file entry dovecot: Dovecot starting up Apr 7

Hello, This bug affects all LLVM versions from 2.6 to trunk : http://llvm.org/bugs/show_bug.cgi?id=5081 The workaround I found is to add this : Index: lib/Target/X86/X86Instr64bit.td =================================================================== --- lib/Target/X86/X86Instr64bit.td (revision 105882) +++ lib/Target/X86/X86Instr64bit.td (working copy) @@ -1832,6 +1832,8 @@

On Jul 7, 2010, at 11:20 AM, Eric Christopher wrote: > > On Jul 7, 2010, at 4:52 AM, Patrick Marlier wrote: > >> Which one is correct ? >> - movl $tm_nest_level at TPOFF, %ecx >> or >> - movq $tm_nest_level at TPOFF, %rcx >> or >> - movl tm_nest_level at TPOFF, %ecx >> > > I believe this is initial exec and so from: > >

On Jun 21, 2010, at 2:56 AM, Patrick Marlier wrote: > Hello, > > This bug affects all LLVM versions from 2.6 to trunk : > http://llvm.org/bugs/show_bug.cgi?id=5081 > > The workaround I found is to add this : > > Index: lib/Target/X86/X86Instr64bit.td > =================================================================== > --- lib/Target/X86/X86Instr64bit.td

Hi, I'm using version 0.99.10.8 on debian 2.4.26 and am getting this problem, can someone please shed some light over this? Aug 31 13:58:58 xxx imap(someone): file_wait_lock() failed with modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: Resource temporarily unavailable and then: Aug 31 14:00:58 xxx imap(someone): Couldn't lock modify log file

Backtrace:/usr/local/libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB

Hey, list -- Recently we had to reboot some of our dom0''s. We were confused after doing so to discover that some of the resident domU''s had not actually rebooted. Some of the domU''s still had very long uptimes (weeks/months), despite the dom0 having an uptime of just minutes. Apparently, when the "shutdown -r now" command was issued, the dom0 was able to

Steven Vaughan-Nichols at Ziff-Davis said: | Unlike all other previous Microsoft operating systems, XP | Home will simply not work in an office network environment | with NetWare, NT, Samba, or Windows 2000 servers. Period. | You simply can't connect to the servers' domains or their | file/print services. Which sounds like they took the SMB client out... | XP Home also has a built-in

Hi, I am trying to modify visitStoreInst() function in Execution.cpp of LLVM 2.7 to do some extra things. How I can determine whether the stored variable is global or local for some function? Regards, Nayden -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100806/fba58a79/attachment.html>

I would like to know something different than that. How I can determine if the address at which data is stored is part of the heap or part of the stack. Regards, Nayden On Sat, Aug 7, 2010 at 3:22 AM, Patrick Marlier <patrick.marlier at unine.ch>wrote: > >> On 08/07/2010 04:41 AM, Nayden Nedev wrote: >> >>> Hi, >>> >>> I am trying to modify

On 07/07/2010 08:20 PM, Eric Christopher wrote: > > On Jul 7, 2010, at 4:52 AM, Patrick Marlier wrote: > >> Which one is correct ? >> - movl $tm_nest_level at TPOFF, %ecx >> or >> - movq $tm_nest_level at TPOFF, %rcx >> or >> - movl tm_nest_level at TPOFF, %ecx >> > > I believe this is initial exec and so from: > >

Dovecot's transactions often write-lock dovecot.index.log twice (without unlocking in between), and then unlock it twice. Is that intended, or is that a bug? If I read the man pages correctly, double write-locking is pointless but safe. But double unlocking could cause data corruption during the period between the first and second unlocks, because the locks don't nest (are not

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have