Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Using Samba 3.0.23 on a Slackware 10.2 box, Im facing failures on a share which hosts an MS Access database.
After some time around 3 to 10 minutes using (with no problems) a Visual Basic application which uses the Access database, it fails with a run-time error 2147217865(80040e37), saying that MS Jet engine is not able to find the database or a table. The share itself, however, is still working nicely at this point, I can reach the .mdb and .ldb files from this machine.
I tried many combinations of locking schemas from Internet searches, with no success. My current [global] section of smb.conf follows:
guest account = guestuser
load printers = no
printcap name = /etc/printcap
log file = /var/log/samba/%m
socket options = SO_KEEPALIVE TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
max xmit = 16384
max connections = 100
max open files = 100000
max log size = 100
deadtime = 10
keepalive = 60
read raw = no
write raw = no
getwd cache = yes
dos filemode = yes
dos filetimes = yes
dos filetime resolution = yes
encrypt passwords = yes
case sensitive = no
default case = lower
preserve case = yes
short preserve case = no
dos charset = ISO8859-1
unix charset = UTF-8
display charset = UTF-8
defer sharing violations = true
fake oplocks = no
kernel oplocks = yes
level2 oplocks = yes
oplock break wait time = 0
oplock contention limit = 2
oplocks = yes
veto oplock files = /*.mdb/*.MDB/*.ldb/*.LDB/
posix locking = yes
blocking locks = yes
lock spin count = 30
The share is using 777 permissions on the filesystem, to be sure that Access have no problems to create its lock files (.ldbs).
If someone faced this kind of problem before and could help me on this, It will be greatly appreciated.
i have a problem that seems to be the same, at least, the error code is exactly the same: "2147467259" and seems to be about file locking, althought also it tries to use a file "mswinsck.ocx" that doesn't exist in the share (i think it should exist) so i will to do some tests after tomorrow, here leave you some changes i'm going to do about the file locking in my smb.conf:
For the global section:
locking = yes
share modes = yes
oplocks = yes
For the share:
create mask = 0777
directory mask = 0777
I hope some of that options could help you to solve the problem, but also if you get the solution before, it will be greatly appreciated too...