search for: smblocks

Hi all, We are considering moving our VSS database from a Win2K server to a samba server. All clients are Win2K clients. I used the VSS tool "testlock.exe" to make sure the native lock mode can be used. The test was successful, and I saw that an SMBlock transaction was performed, and a reply_lockingX was replied. When I opened a VSS database on the samba server and started to use it -

...smbstatus does not show the lock, however hwen I show byte range locks, there is one, from a PID that doesn't exist. I assume this is the problem lock. The smbd that owned the lock died when the client rebooted/reconnected. I am unable to fix this problem. I think that samba at least needs a smblocks utility to force locks to be released, and manipulate the lock db (is there such a thing) in order to fix solutions like these. When it happens a user on the network is unable to access their email until samba is restarted, which cannot be done during normal working hours... it's becoming a big...

...# roman.gollent@wdr.com # PURPOSE: kill old smbd processes when a client abandons its TCP # connection, establishes a new connections but the Samba # server doesn't know. To be called by smbd as part of share # preexec/postexec configuration. # # (c) 1999, Perot Systems Corporation. SMBLOCKS=/var/locks SMBLOGS=/var/log/smblogs set -o noclobber # Set stderr exec 2>> $SMBLOGS/staleSessions.log print -u2 -- "$@" SELF=${0##*/} OP=$1 SMBPID=$2 SMBCLIENT=$3 SMBSERVER=$4 SMBSERVICE=$5 SMBUSER=$6 status="" # This sets the name of the pid file for this # {client,...

Thanks torch ? I tried those suggestions but nothing changed. I did however manage to find an existing bug which matches my symptoms: https://bugzilla.samba.org/show_bug.cgi?id=13622 Fortunately it mentions a fix, but that was never implemented, so I created a new branch from v4-11-test on the gitlab shadow copy and tried the fix there. After compiling, my tests on Raspbian show that this does

Hi I apt installed Samba Version 4.9.5-Debian (latest in their repos) on a fresh-built Raspbian Buster Lite release 2020-02-05. I put together the configuration outlined below by using the docs at https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X and https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html. The underlying usb hard drive is an ext4 partition