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. -- Jefferson K. Davis Technology and Information Systems Manager Standard School District 1200 North Chester Ave Bakersfield, CA 93308 USA 661-392-2110 ext 120
On Fri, Sep 17, 2004 at 10:34:28AM -0700, Jeff Davis 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.FC2What database ? What clients ? Are you running the updated redirector fixes ? Are you getting any error messages in the logs ? Thanks, Jeremy
> veto oplock files = /*.mdb/*.ldb/*.mdw/*.dbf/*.dat/*.fptIs it a good idea to not allow the .ldb files? I was under the assumption that you pretty much need a .ldb file to keep an access db sane when multiple people are using it. -- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Information Systems Consultant Fax: 701-281-1322 URL: ae-solutions.com mailto: pgienger@ae-solutions.com
> -----Original Message----- > From: Jeff Davis [mailto:jdavis@standard.k12.ca.us]> 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.How many users? My experience suggests that once you get over four or five users, Access databases do this no matter what operating system they're hosted on. :P
On Friday 17 September 2004 12:11, Paul Gienger wrote:> > veto oplock files = /*.mdb/*.ldb/*.mdw/*.dbf/*.dat/*.fpt > > Is it a good idea to not allow the .ldb files? I was under the > assumption that you pretty much need a .ldb file to keep an access db > sane when multiple people are using it.The procedure for protection of MS Access databases under multi-user operation is documented in the Samba-3 By Example Appendix 8.1. You can obtain this from Amazon.Com or from: samba.org/samba/docs/Samba-Guide.pdf If the information you find there is does not solve the problem please let me know so I can fix it. - John T.> > -- > Paul Gienger Office: 701-281-1884 > Applied Engineering Inc. > Information Systems Consultant Fax: 701-281-1322 > URL: ae-solutions.com mailto: pgienger@ae-solutions.com-- 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.
> 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 ?> -- > 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: lists.samba.org/mailman/listinfo/samba >