similar to: No filelocking at "shared-mailboxes" dictionary?

Hi Felix, On 4/18/24 08:33, Stolte, Felix via samba wrote: > Is this a bug or maybe a misconfiguration? In the latter, which parameters could cause this? I guess the nodes end up using different combinations of dev/inode as primary key for the locking.tdb record. Probably because the device numbers differ on the nodes and you didn't fix this known issue with GPFS with the fileid VFS

Hi there, is it possible and when, how - to change the filelocking-status of an opened file from EXCLUSIVE+BATCH to another status ? We have to open an file to write at the same time from different pc's into this file. For example the following smbstatus -u USER output: Pid DenyMode Access R/W Oplock Name DENY_DOS 0x1 RDONLY EXCLUSIVE+BATCH

Hi, Can someone give me some pointer or links to understand how Filelocking and rquotad works on NFS ? I searched a lot on google , didn't get any good articles on that. -- Regards Basil

Hi there, we've got the following problem, while Windows-Clients works with samba and a DOS-Client connects over Mars_NWE to the same Linux-Server: When the DOS-Client opens a file on the linux-server and the WinClient opens the same file, and when both clients want to write the same file, the windows-client gets an error and crashes. We tried it only with the windows-clients and there

Hi folks, we are running a clustered Samba Fileserver using CTDB with two public IPs. We observed the following (mis) behavior: If user A with write permissions opens an excel file via public ip A and User B opens the same file via public ip B, both users get a Deny-Write lock on the same file and overwrite each others changes: 0:3693691 145522 DENY_WRITE 0x12019f RDWR

Hi, first of all, please CC me on any reply, as I am only subscribed to the digest. OK. Here is the problem. Said kernel (from 4.4) seems to have problems with file-locking when the system is under high, likely network related, load. The symptoms are things using file locking (rpm, the user-space automounter amd) fail to obtain locks, usually stating timeout problems. The sytem in question is

Ok, you are completely right. Here are the real numbers with changed user names: drwx------ 43 DOM\user1        DOM\domain-user  4096 Jan 10 08:00 user1 drwx------   5 DOM\user2        DOM\domain-user  4096 Jan 11 08:13 user2 drwx------ 92 DOM\user3        DOM\domain-user   4096 Jan 16 08:39 user3 drwx------   3        133265        DOM\domain-user   4096 Sep  7 2015 user4 drwx------   7       

Am 16.01.2018 um 17:26 schrieb Rowland Penny via samba: > On Tue, 16 Jan 2018 16:54:17 +0100 > Andreas Hauffe via samba <samba at lists.samba.org> wrote: > >> Ok, you are completely right. Here are the real numbers with changed >> user names: >> >> drwx------ 43 DOM\user1        DOM\domain-user  4096 Jan 10 08:00 >> user1 drwx------   5 DOM\user2       

http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz.sig Looks like it took a bit longer to make this release after RC1 than I thought. I'm now in San Jose area for a few months and still jumping between apartments and trying to adjust to the new timezone. Some of the more important fixes since RC1: - Fixed several race conditions with

http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.14.tar.gz.sig Looks like it took a bit longer to make this release after RC1 than I thought. I'm now in San Jose area for a few months and still jumping between apartments and trying to adjust to the new timezone. Some of the more important fixes since RC1: - Fixed several race conditions with

On Tue, 16 Jan 2018 16:54:17 +0100 Andreas Hauffe via samba <samba at lists.samba.org> wrote: > Ok, you are completely right. Here are the real numbers with changed > user names: > > drwx------ 43 DOM\user1        DOM\domain-user  4096 Jan 10 08:00 > user1 drwx------   5 DOM\user2        DOM\domain-user  4096 Jan 11 > 08:13 user2 drwx------ 92 DOM\user3       

Hi, I just installed dovecot 1.0 beta 7 and I have these errors: May 5 09:21:27 mail dovecot: pop3-login: Login: user=<user1>, method=PLAIN, rip=::ffff:xx.xx.xx.6, lip=::ffff:xx.xx.xx.1 May 5 09:21:27 mail dovecot: POP3(user2): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 May 5 09:21:27 mail dovecot: pop3-login: Login: user=<user3>, method=PLAIN,

Hi Andreas, i'm sorry to jump on your thread as i can't really help you here. But as i have to setup an AD subdomain of a parent domain with the same requirements as yours apparently (aka parent domain managed by Windows server holds users/groups accounts on a distant location but the compute ressources and the GPO will be managed locally under a subdomain), i'm just wondering if you

Hi, no, that's my fault. I changed the UIDs and user names in my "ls -l" to unpersonalized/example data for my mail and didn't think about putting these values into the range. A better unpersonalized data example would look like: ---------- drwx------ 43 DOM\user1        DOM\group  4096 Jan 10 08:00 user1 drwx------   5 DOM\user2        DOM\group  4096 Jan 11 08:13 user2

Hi all, I'm trying to resolve a weird issue with SIP routing. I have a number of SIP trunks, from a selection of providers, all of which are registered in sip.conf: [general] context=default allowguest=no allowoverlap=no udpbindaddr=0.0.0.0 tcpenable=yes tcpbindaddr=0.0.0.0 transport=udp bindport=15060 srvlookup=yes allowsubscribe=yes

Hi, yes, there are some things. But I have not found a nice complete documentation. One main point is the domain name as prefix of the username of the parent domain, e.g. "DOM\user1", you have to use. I was not able to get rid of it, as the client is member of the subdomain which is the default. So you can't use the "default domain" option in smb.conf. The backslash

Hi, Jan 26 17:21:40 doveadm(user7 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:23:59 doveadm(user3 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:24:44 doveadm(user5 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused Jan 26 17:24:44 doveadm(user4 at domain.ltd): Fatal:

Hello, I am trying to define a share that is write accessible by only a two individuals, and read-only for a few other individuals. Everyone else doesn't get access to the share. My smb.conf entry for the share is below [soldrequest] comment = Soldrequest polling share path = /soldrequest read only = yes guest ok = no valid users = user1,user2,user3,user4,user5,user6,user7,user8

I'm trying to store mailboxes in a cloudfile system and I am running into alot of problems using courier, between time skew, file locking and cache creation problems. I was wondering if dovecot has any problems using maildirs across a limited fuse file system. I cant lock files, This is accessed using the fuse library. I thought taking out the standard checking for return values would be a

I am seeing many, many msgs in log.winbindd with the following text: [2006/04/14 08:54:29, 1] nsswitch/winbindd_group.c:winbindd_getgrnam(255) group system in domain AIXSAMBA does not exist Would anybody be able to point me in the right direction to determine what this is complaining about? One area I do not understand is why it is complaining about AIXSAMBA (the NETBIOS name). There is an