search for: byteranges

...uld' portability to the existing inotify-like APIs on most mainstream operating systems is very possible and expected. * The maximum useful value for /proc/sys/fs/inotify/max_user_watches is 32768 . Which is quickly exceeded on any moderate Maildir deployment. * inotify has no concept of byteranges to indicate where a modification happened. Architecture Discussion ----------------------- * inotify is about extending specific Linux filesystems. But replication ought to be as filesystem-independent as possible as well as independent of operating sytems and versions, so inotify is not id...

from smbstatus man page: -B|--byterange causes smbstatus to include byte range locks. the fact is that 4 different connections are opening the same byte range in 'MOVCTA.cdx' That's about all that I can get from your command result dump. On 2018-11-22 9:21 a.m., Jose Concha wrote: > Using oplocks = no makes the communication extremely slow. For testing >

Hallo, in 3.0.8pre2 the smbstatus command always shows connections _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for showing locks only: test2 # smbstatus --help Usage: [OPTION...] -p, --processes Show processes only -v, --verbose Be verbose -L, --locks

Hello, I've been working with a xBase database (similar to dBase) in a multiuser application. There are like 40 users working on the database on the same time reading and like 10 writing information. Sometimes the CDX files (Index Files) get corrupted and is it's necessary to pack the tables (rebuild the indexes). I have notice using the smbstatus -B command the following Pid