samba record locking
Mark Szidik
szidikm@mlc.lib.mi.us
Fri, 20 Oct 2000 16:28:27 -0400 (EDT)
Have you tried to set the oplocks=no option on that share? How about
oplock files=no ?
I don't claim to know exactly what these will do, but you can try them.
______________________________________________________________________
Mark Szidik
System Administrator Ph: 517.694.4242 x17 Fax: 517.694.9303
Michigan Library Consortium http://www.mlc.lib.mi.us
On Fri, 20 Oct 2000, Mike Rambo wrote:
> I got back out to our Linux server at ForestView today. It appears the
> problem with accessing some of the server apps is one of record
> locking. A program called Accelerated Reader is one of the critical
> apps we must have available to all workstations. Basically what I've
> found it that it's useable by all stations as long as it is done one at
> a time.
>
> Can anyone explain how record locking is handled with samba? The server
> is set up with share security and although share modes = yes is default
> I have also explicitly stated it too. This particular app is among a
> few that need write access to data files and a temp directory. All of
> the apps have been made public read only shares with the write access
> granted to those directories that need it. I don't really know how the
> app itself handles it's data updates with multiple users but I do know
> that this program is working on other Novell and NT servers so it should
> work with Linux.
>
> Any idea's would be very much appreciated.
>
>
> --
> Mike Rambo
> mrambo@lsd.k12.mi.us
> _______________________________________________
> linux-user mailing list
> linux-user@egr.msu.edu
> http://www.egr.msu.edu/mailman/listinfo/linux-user
>