On Sunday 19 September 2004 03:33, Ilia Chipitsine wrote: > > Ok, I've tried all the "common" fixes, such as turning oplocks off on the > > share. Twice a day the database has to be repaired. > > > > running samba-3.0.7-2.FC2 > > > > Here's the pertinent section: > > > > comment = Aeries > > path = /home/aeries > > valid users = @aeries > > read only = No > > create mask = 0770 > > directory mask = 0770 > > inherit permissions = Yes > > veto oplock files = /*.mdb/*.ldb/*.mdw/*.dbf/*.dat/*.fpt > > oplocks = No > > level2 oplocks = No > > > > Any ideas? Unforunately killing off msaccess is not an option. > > there's a special quirk for MS Access described in Samba-Official-Howto > > but the question is: why special handling required for Samba and is not > required for w2k server ? can samba detect this situation "on the fly" ? > just like the way w2k server does ?
No, w2k does NOT auto-detect any locking requirements for MS Access. Suggest you check the MS knowledge base references in Samba-Guide.pdf Appendix 8.1. - John T. > > > -- > > Jefferson K. Davis > > Technology and Information Systems Manager > > Standard School District > > 1200 North Chester Ave > > Bakersfield, CA 93308 > > USA > > 661-392-2110 ext 120 > > > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: http://lists.samba.org/mailman/listinfo/samba -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 OpenLDAP by Example, ISBN: 0131488732 Other books in production. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
