search for: op_locks

...ue lpq command = /usr/bin/lpstat -o %p printing = bsd printcap name = /usr/local/samba/lib/printcap load printers = yes print command = lp -d%p -oraw -s %s; rm %s lprm command = /usr/bin/cancel %p-%j ; locking = yes << I've turned this on & off -- no change ; op_locks = true << ibid (also fake oplocks) [tmp] ; map to D: ; We're NOT preserving case here (everything goes lowercase) as it breaks ; several shell scripts relating to payroll data IMPORT. comment = temporary files path = /tmp read only = no public = yes create mode = 0644...

...the switcher was malfunctioning) and tons of other scenarios. Nothing! Zilch! Unfortunately I am faced with a very serious problem since this occurs every week (sometimes more than 3 times a day!!!). Looked in google for this. Another person who had the same problem had a solution published with op_locks etc, tried that...nothing! Can someone give me a good idea?? Thank you tons! Chris PS: Samba is running on SuSE Linux 9.1 Samba 3.0.2a-51

Hi all, SAMBA pre2.0.7 ./configure --with-quotas Linux 2.0.36 The old disk quota bug is still here. If user tries to write the file to SAMBA share and disk quota is exceeded, SAMBA fills remaining space within the target file with spaces, and writes it to the share. This is "xcopy" behavior. If the program writes small chunks of file, the result may differ. The user is under