>Number:         8560
>Category:       pkg
>Synopsis:       
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager (NetBSD software packages system bug manager)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct  5 06:05:00 1999
>Last-Modified:
>Originator:     Jeroen Scheerder
>Organization:
	
>Release:        1.4.1
>Environment:
	
System: NetBSD dek 1.4.1 NetBSD 1.4.1 (JS) #1: Fri Sep 17 12:56:09 MEST 1999 js@dek:/usr/src/sys/arch/i386/compile/JS i386


>Description:
	previously described Mutt locking problem
>How-To-Repeat:
	
>Fix:
Earlier today, I described a scenario in which mutt would fail dotlocking
a mailbox (nfs-hosted, typically) after a successful fcntl.

According to the mutt developer, this is correct behaviour, and the proper
fix, for system bitten by this, is to have mutt's config reflect the
"corporate mailbox locking strategy" a bit closer.  Specifically,
in my case, disabling dotlocking does the trick:

*** config.h.org        Tue Oct  5 14:49:47 1999
--- config.h    Tue Oct  5 14:23:43 1999
***************
*** 63,69 ****
  /* #undef DOMAIN */
  
  /* use dotlocking to lock mailboxes? */
! #define USE_DOTLOCK 1
  
  /* use flock() to lock mailboxes? */
  /* #undef USE_FLOCK */
--- 63,69 ----
  /* #undef DOMAIN */
  
  /* use dotlocking to lock mailboxes? */
! /* #define USE_DOTLOCK 1 */
  
  /* use flock() to lock mailboxes? */
  /* #undef USE_FLOCK */
>Audit-Trail:
>Unformatted: