Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.6: Fix a file copy issue with SMB, XBMC, and Xbox' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: Fix a file copy issue with SMB, XBMC, and Xbox
Authored by: qrulf on Feb 18, '10 05:29:10AM
From man smb.conf:
strict locking (S)
This is an enumerated type that controls the handling of file locking in the server. When this is set to yes, the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on some systems.

When strict locking is set to Auto (the default), the server performs file lock checks only on non-oplocked files. As most Windows redirectors perform file locking checks locally on oplocked files this is a good trade off for inproved performance.

When strict locking is disabled, the server performs file lock checks only when the client explicitly asks for them.

Well-behaved clients always ask for lock checks when it is important. So in the vast majority of cases, strict locking = Auto or strict locking = no is acceptable.

Default: strict locking = Auto


[ Reply to This | # ]