search for: check_file_shar

...share on my RedHat machine. We were finding that she couldn't rename any MP3s on the Samba share: she would always get a sharing violation. After a day of reading Samba logs at debug 10 (_such_ fun [ ;) ]) and adding debug information so I could figure out what was up, I found some oddness in check_file_sharing. It was always reporting the MP3s as having a single share mode of op_type _0_, locked by the Samba server that was trying to do the rename. op_type 0 seemed to imply an unlocked share, so I went in to see if I could tweak the server to work in that case. A full patch (including a TON of DEBU...

I saw a little discussion about this a few weeks ago but nothing concrete. We're running samba-1.9.18p8 under Solaris 2.6x86. I am periodically getting the following in the logfiles, usually _many_ at a time: 1998/11/03 14:42:00 request_oplock_break: no response received to oplock break request to pid 5411 on port 40884 for dev = 1980040, inode = 33c4d When I look up the PID (in this case

...log files again and now understand that the problem is related to opportunistic locking. I also found the part of the log file that details the start of the event. Here it is: 1998/06/19 15:51:19 ukswi1000 (175.12.50.218) connect to service its as user bramsons (uid=10808,gid=11000) (pid 25917) check_file_sharing: NT redirector workaround - rename attempted on batch oplocked file samba-tests/~WRD0000.tmp, dev = ff00061a, inode = 3b20b check_file_sharing: NT redirector workaround - rename attempted on batch oplocked file samba-tests/~WRD0002.tmp, dev = ff00061a, inode = 3b20d can't open username map /...

...$2") local result if [ "x$mode" = 'x!' ] then return 0 fi result=$(check_sharing "$dev" "$mode") if [ "$result" != 'ok' ] then do_ebusy "Device $dev is mounted " "$mode" "$result" fi } check_file_sharing() { local file="$1" local dev="$2" local mode="$3" result=$(check_sharing "$dev" "$mode") if [ "$result" != 'ok' ] then do_ebusy "File $file is loopback-mounted through $dev, which is mounted " "$m...

Has anyone tried using Windows 2000 Professional with Samba? I'm checking it out now, and when I try to connect to a share, I get an error message similiar to the one you get with Win98 and NT4 with SP3+ with encrypted passwords. Does anyone know the equivelant registry path to set plain text passwords? The NT4 path doesn't seem to exist:

Hi, I'm running smbd 2.2.8. I'm a little green when it comes to file locking with samba. I have two users that access a single data file on a FreeBSD box. It's a moneydance data file and obviously it gets messed-up if two users are writing to it at the same time. Is there a way with samba to stop a second instance of the file from being opened, something like a "File In