Comment 20 for bug 198351

Not actually related to the defect but I've just bumped into it. Intensive multithreaded access to the same files on a share (in my case, make command run in parallel mode using four threads) causes problems (sporadic errors like 'no such file or directory' or 'file read error' that disappear after a re-run of the command) with the downgraded version of libsmbclient too. However, fusesmb suffers much more from that problem than smbnetfs. If I limit the number of threads to just one (make -j 1) the problems disappears completely (both in fusesmb and in smbnetfs).