similar to: best practice nfs and samba file lock

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

http://dovecot.org/tools/nfstest.c I wrote a test utility that tests different ways to flush NFS attribute cache and data cache. Please test in your NFS setup and show me the results, so I can make Dovecot v1.1 works well with NFS. Run the test several times (3 should be enough) to make sure the output stays the same, because the attribute cache flushes might incorrectly say "OK". And

Hello, Iam facing a problem in locking of files across samba shares. We have samba 3.0.10 running on Solaris 9 with the smb.conf as follows. # Global parameters [global] workgroup = NMUINT netbios name = NMUINTFS interfaces = <IP> bind interfaces only = Yes security = DOMAIN password server = XXX.XXX.XXX.XXX log level = 1 ldap

I've finally managed to run Dovecot without errors in two computers with maildir and indexes stored in NFS. I added a page to wiki about this: http://wiki.dovecot.org/NFS Suggestions how to keep attribute cache enabled but to allow Dovecot to specifically request not to use a cached value (when it's important) would be welcome. -------------- next part -------------- A non-text

Hey, we are using rhel7 with samba and winbind packages from redhat. it is a fileserver joined to samba 4 domain. os: rhel7.4 samba-winbind-4.6.2-12.el7_4.x86_64 samba-winbind-clients-4.6.2-12.el7_4.x86_64 samba-winbind-modules-4.6.2-12.el7_4.x86_64 approx. 350 clients approx. 10000 open files see attached stripped smb.conf the following problem exist: after a time (several hours) the

Thanks Michael, after starting the service within a few secs it dies in my case with this error samba winbind Got sig[15] terminate (is_parent=1) Let me know if you need any further information. Many Thanks On Thu, Nov 23, 2017 at 4:54 PM, Michael Wandel <m.wandel at t-online.de> wrote: > On 23.11.2017 17:49, Arnab Roy wrote: > > Hi Michael, > > > > I didnt change

Dear Colleagues, I use exim's appendfile transport, procmail and a local mutt on my system, they all (to my knowledge) use lockfiles when working with mboxes. However, `doveconf | grep lock` says dotlock_use_excl = yes lock_method = fcntl mail_max_lock_timeout = 0 mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl

On Tue, 9 Oct 2018 12:08:00 +0200 Sami Ketola <sami.ketola at dovecot.fi> wrote: > How do you deliver then mails to the server? > > also mbox is very unoptimised mailbox format for this. Each time mail is deleted from mbox mailbox the whole mbox while needs to be rewritten to remove the mail. OpenSMTPD and Dovecot run on the same machine. OpenSMTPD receives incoming mails and

Hi all, I have some machines running FreeBSD and dovecot deployed. User's home dir is on NFS mount and I've found that dovecot only works with dotlock file locking mechanism, fcntl and flock failed. Now it causes problem with thunderbird (thunderbird is cachine connections) waiting forever and I noticed that dovecot is trying to acquire a lock but unsuccessful since the lock file is in

What syntax is needed to make this work? The 2.0 wiki recomendations don't work - I can see the inboxes or the folders but not both at once and there are lots of error messages about prefix clashes if I simply use the existing 2.0.20 conf file on 2.1.6 The layout I have is: Inboxes in mbox format - /var/spool/mail/%u Folders in maildir format - /var/spool/imap/%u/Maildir/ Control and

http://dovecot.org/rc/ Thought I'd still make one 0.99.10.x release now that mbox corruption problems are (hopefully) fixed. Please test, if no problems are found this will be the final 0.99.10.5. Changes since .4: + MySQL authentication, patch by Matthew Reimer - mbox: APPEND reversed given \Draft and \Deleted flags - mbox: "LF not found" errors happened sometimes when

Hi, currently I have one new user with a problem. When she logs in to dovecot with pop3 from her apple mail, dovecot tells problems with the +w permission. Error: open(/var/mail/******) failed: Permission denied (euid=3462(******) egid=548(dozenten) missing +w perm: /var/mail) /var/mail is rw by root.mail I cant see why just this particular user has that problem/gets that messages. AFAIK no

Hello, I have some trouble with the current setup (it's a testing environment): 2 server with Dovecot 1.1.4 from source (OS Debian testing 2.6.26) (name: "exim" and "exim2") 1 NFS server (OS Debian testing 2.6.26) I use NFS v.4, indexes shared over NFS. The relavant part of Dovecot configuration: dotlock_use_excl = yes mail_nfs_storage = yes mail_nfs_index = yes

Is dovecot still considered unreliable when combined with NFS? Is this true for mbox only, or Maildir as well? If dovecot Is still considered unreliable with NFS, how about having a dovecot mode that would chain into procmail for delivery, so that dovecot doesn't (necessarily) have to reinvent that wheel? Thanks!

While doing migration, sometimes found suspend lock file was not unlinked in previous operations, then there is an obsolete lock file in place, which causes the current and later migration cannot get lock. That happens seldomly but do happen. After checking the source code, I found there are some places that potentially cause lock file unlinked, including: 1) in lock_suspend_event() function,

Hi, I see samba with ctdb locking has following mapping when kernel oplocks = yes. share mode reservations = flock(2) posix byte range locking = fcntl(2) SMB locks (mandatory) = ctdb using brlock.tdb oplocks = fcntl(2) using F_SETLEASE Am I correct or I am missing something? I hope only SMB range locks are implemented with tdb, all else are being used from filesystem. What

Hi, may be there are some best practice suggestions for the "best mode" for channel bonding interface? Or in other words, when should/would I use which mode? E.g. I do have some fileservers connected to the users lan and to some ISCSI Storages. Or some Webservers only connected to the LAN. The switches are all new cisco models. I've read sone docs (1), (2) and (3) so the theory

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

Hi - I'm trying to verify if OpenSSH/SFTP will in fact lock files with advisory file locking in Linux. I can test locking with the linux "flock" command to verify that file locking does work - but when I upload or download a file with SFTP it will not detect a lock. I'm asking about Linux specifically because about a year ago I was doing a similar process in Solaris 9 and