[Samba] Oplocks on Windows Clients and Winbind revisited
The Fresh Prince of Darkness
ghstwrtr at evilgenius.net
Fri May 16 17:25:56 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
First, the more I read about olocks the more inclined I am to disable
them globally. Here's the issue though, after experiencing data
corruption in Act files at the hands of oplocks, we checked the Act
support database and they recommended disabling oplocks not only on the
server, but on the client machine as well. Is there any reason why this
should be necesary? If I disable oplocks for all my shares, should I
disable it on my client machines as well. We're using NT & 2k mostly,
with an occasion xp or 98 box, but not many.
Also, last week I'd asked about syncing winbind databases. It was
suggested that backing up the winbind_idmap.tdb would be sufficient to
restore the proper mappings upon failure. I tried an experiment with
another linux box wherein as a nightly cron job, the machine shuts down
winbind locally and on the master machine, copies the tdb over from the
master and then re-starts winbind again. This was successful in
reproducing the same mappings as on the master machine. What is the
downside to doing this on production servers?
Thanks.
- -Ron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+xR8ovsPR55EQ+eIRAuZAAJ9IDoKt81AuirAsbBMdLN/KNky1fQCgkrOk
m8qBLCBDBIofVuDXE+/xV1M=
=W9Wh
-----END PGP SIGNATURE-----
More information about the samba
mailing list