search for: fcntl

Hello, I'm using samba 4.7.3 to run an AD and I'm currently having issues with the MIT kerberos because it stops some time after starting (and apparently working correctly) without logging nothing out of the ordinary. My setup has 2 DC: one in an ubuntu 12.04 with version 4.1.9 (which we're migrating from) and the one I mentioned in CentOS 7 (which will be the only DC in the future).

...1399964809 time(NULL) = 1399964809 time(NULL) = 1399964809 time(NULL) = 1399964809 time(NULL) = 1399964809 time(NULL) = 1399964809 fcntl(12, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=32544, len=1}) = 0 fcntl(12, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=32544, len=1}) = 0 fcntl(12, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=32544, len=1}) = 0 fcntl(12, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET...

...1, > 30000) = 1 > readv(91, > [{"\34\0\0\0\0\0\0\0rT\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2092}], > 1) = 2092 > gettimeofday({1419854003, 222035}, NULL) = 0 > gettimeofday({1419854003, 222103}, NULL) = 0 > gettimeofday({1419854003, 222169}, NULL) = 0 > fcntl(16, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=176, len=1}) = 0 > fcntl(16, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=176, len=1}) = 0 > gettimeofday({1419854003, 222345}, NULL) = 0 > gettimeofday({1419854003, 222482}, NULL) = 0 > gettimeofday({1419854003, 222868}, NULL) = 0...

...\0\0\0\0\0\0rT\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., >>> 2092}], >>> 1) = 2092 >>> gettimeofday({1419854003, 222035}, NULL) = 0 >>> gettimeofday({1419854003, 222103}, NULL) = 0 >>> gettimeofday({1419854003, 222169}, NULL) = 0 >>> fcntl(16, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=176, >>> len=1}) = 0 >>> fcntl(16, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=176, >>> len=1}) = 0 >>> gettimeofday({1419854003, 222345}, NULL) = 0 >>> gettimeofday({1419854003, 222482}, NULL) = 0...

Hi, I'm having problems in a second domain controller machine. Every time a restart samba, few time after a samba process starts using almost 100% cpu. It's a Centos 6.5 x86_64 with the following: sernet-samba-libsmbclient0-4.1.6-7.el6.x86_64 sernet-samba-ad-4.1.6-7.el6.x86_64 sernet-build-key-1.1-4.noarch sernet-samba-libs-4.1.6-7.el6.x86_64 sernet-samba-client-4.1.6-7.el6.x86_64

Hi, this is an old problem it was worse in the pre-3.5.0 releases, on solaris 10 all the cpu gets consumed by fcntl calls: 7963: fcntl(22, F_SETLKW64, 0xFFBFE050) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFDE78) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFDF58) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFDF70) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFE050)...

...{u32=2539833808, u64=140271876753872}}}, 1, 30000) = 1 readv(91, [{"\34\0\0\0\0\0\0\0rT\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2092}], 1) = 2092 gettimeofday({1419854003, 222035}, NULL) = 0 gettimeofday({1419854003, 222103}, NULL) = 0 gettimeofday({1419854003, 222169}, NULL) = 0 fcntl(16, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=176, len=1}) = 0 fcntl(16, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=176, len=1}) = 0 gettimeofday({1419854003, 222345}, NULL) = 0 gettimeofday({1419854003, 222482}, NULL) = 0 gettimeofday({1419854003, 222868}, NULL) = 0 fcntl(13, F_SETLKW,...

...readv(91, >> [{"\34\0\0\0\0\0\0\0rT\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2092}], >> 1) = 2092 >> gettimeofday({1419854003, 222035}, NULL) = 0 >> gettimeofday({1419854003, 222103}, NULL) = 0 >> gettimeofday({1419854003, 222169}, NULL) = 0 >> fcntl(16, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=176, len=1}) = 0 >> fcntl(16, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=176, len=1}) = 0 >> gettimeofday({1419854003, 222345}, NULL) = 0 >> gettimeofday({1419854003, 222482}, NULL) = 0 >> gettimeofday({1419854003, 222...

...\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., >>>> 2092}], >>>> 1) = 2092 >>>> gettimeofday({1419854003, 222035}, NULL) = 0 >>>> gettimeofday({1419854003, 222103}, NULL) = 0 >>>> gettimeofday({1419854003, 222169}, NULL) = 0 >>>> fcntl(16, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=176, >>>> len=1}) = 0 >>>> fcntl(16, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=176, >>>> len=1}) = 0 >>>> gettimeofday({1419854003, 222345}, NULL) = 0 >>>> gettimeofday({1419854003,...

Hi, I am still struggling with the printing in a AD2008 R2 environment I changed to 3.2.15 by now. Still very slow, I am running on solaris 10. Not sure if my clients are so chatty by now but it is really killing any performance. Using truss I see loads of: 19702: fcntl(17, F_SETLKW64, 0xFFBFE640) = 0 19702: fcntl(17, F_SETLKW64, 0xFFBFE150) = 0 19702: fcntl(17, F_SETLKW64, 0xFFBFE218) = 0 19702: fcntl(17, F_SETLKW64, 0xFFBFE578) = 0 19702: fcntl(17, F_SETLKW64, 0xFFBFE640) = 0 19702: fcntl...

...em has started to reappear with our Solaris (2.8) Samba (3.0.23b). This was after an upgrade from 3.0.22 in which the problem was worse. Occasionally an smbd process will go "rogue" and start consuming CPU cycles until killed. I did a truss of the process and got back this tight loop. fcntl(27, F_SETLKW64, 0xFFBEEF98) = 0 fcntl(27, F_SETLKW64, 0xFFBEF010) = 0 fcntl(27, F_SETLKW64, 0xFFBEF208) = 0 fcntl(27, F_SETLKW64, 0xFFBEF280) = 0 time() = 1156517189 fcntl(27, F_SETLKW64, 0xFFBEEEC8)...

...server 28923 rpc_server 28923 rpc_server 28923 rpc_server 28923 dreplsrv 28930 dc000:~# strace -p 28923 -f strace: Process 28923 attached strace: [ Process PID=28923 runs in x32 mode. ] strace: [ Process PID=28923 runs in 64 bit mode. ] fcntl(15, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=332, l_len=1}) = 0 fcntl(15, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=368, l_len=1}) = 0 fcntl(15, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=5073496, l_len=1}) = 0 fcntl(15, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_S...

Thanks for answer. I am very sad to see that. I had examined samba behavior with tracer and had seen too many poll, fcntl and stat system calls by samba task[ldapsrv] process Elapsed Times for PID 1423, SYSCALL TIME (ns) dup 2653 flock 5811 lseek 33513 geteuid 42747 getpid...

Hello, I have a question regarding mailbox locking and hope any one can help me to better understanding the locking of mbox My Postfix lock option is fcntl dotlock mailbox_delivery_lock = fcntl, dotlock virtual_mailbox_lock = fcntl, dotlock My Dovecot lock option is fcntl only mbox_write_locks = fcntl mbox_read_locks = fcntl now, when user is download a large mail (20 MB) for example, dovecot locks /var/mail/user with fcntl until the users finish...

...contact a DC because the IPv6 connect fails immediately before the v4 connect has a chance to succeed. I determined this by strace'ing the "net ads workgroup" command, which resulted in the following: 11:41:52 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 11 <0.000027> 11:41:52 fcntl(11, F_GETFL) = 0x2 (flags O_RDWR) <0.000015> 11:41:52 fcntl(11, F_SETFL, O_RDWR|O_NONBLOCK) = 0 <0.000016> 11:41:52 fcntl(11, F_GETFD) = 0 <0.000015> 11:41:52 fcntl(11, F_SETFD, FD_CLOEXEC) = 0 <0.000016> 11:41:52 connect(11, {sa_family=AF_INET, sin_port=htons(389), sin_addr...

...path = /mnt/fratar-btrfs/profiles read only = No hide files = /desktop.ini/$RECYCLE.BIN/ vfs objects = btrfs [users] path = /mnt/fratar-btrfs/users read only = No vfs objects = btrfs strace -p PID is giving a lot of messages like these: fcntl(9, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=168, l_len=40000}) = 0 fcntl(9, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=40168, l_len=0}) = 0 fcntl(12, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=168, l_len=40000}) = 0 fcntl(12, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK...

The previous code: fcntl (fd, F_SETFL, O_NONBLOCK) was technically incorrect, because it would have reset any other flags on the file descriptor. Thanks: Eric Blake --- bootstrap | 1 + daemon/inotify.c | 6 ++++-- lib/conn-socket.c | 21 +++++++++++---------- m4/.gitignore | 9 +++++++++ 4 files changed...

..., you could try stracing the process (strace >-ttT -p <pid>) and see what it does. gstack <pid> also helps >often. We got the following strace over the samba process 'locked' *[PRO]* [root at pf3il0024 ~]# strace -p *38063* Process 38063 attached - interrupt to quit fcntl(39, F_SETSIG, 0x23) = 0 fcntl(39, F_SETLEASE, F_WRLCK) = 0 getxattr("tf-PRENSA_DIRLOG_20141202_100852", "system.posix_acl_access", 0x7fff5f0b8320, 132) = -1 *ENOENT* (No such file or directory) getxattr("tf-PRENSA_DIRLOG_20141202_100852", &quo...

https://bugzilla.netfilter.org/show_bug.cgi?id=1104 Bug ID: 1104 Summary: Use close on exec flags instead of fcntl Product: iptables Version: CVS (please indicate timestamp) Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: iptables Assignee: netfilter-buglog at lists.netfilter.org...

...ding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? - when a process abort trying to get a lock after mbox_lock_timeout, does the UA sees anything ? - multiple locking methods in "mbox_write_lock" : if I state, for instance, mbox_write_locks = dotlock fcntl when does exactly do...