Sometimes you need to reboot the workstation to flush it's cached data. Tom Dickson ([EMAIL PROTECTED]) wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What is the standard procedure for making edits of smb.conf take hold? > > For example, what I'm seeing is a share that has given R/W access to a > user named Tom, when I change Tom to read only, he is still able to > write to that share until I stop Samba and restart it. > > The documentation seems to refer to a 1 minute reread of smb.conf, but I > don't seem to see that taking hold. > > Thank you! > > - -Tom > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFAZIve2dxAfYNwANIRAiH6AJ9HSZ6KlzBQYA+bZPjNeGTW5HH9+gCeOm/3 > OLLvb9WyE2kyR+BJt6l712U= > =OBG+ > -----END PGP SIGNATURE----- >
-- Assured Computing, Inc. When you need to be sure. http://www.assuredcomp.com/ P.O. Box 40814 Eugene, OR 97404 Voice - 541-868-0331 FAX - 541-463-1627 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
