At our lab we have 200 clients which are mounting to samba share. On some clients a certain file has a different checksum than the others. This is causing many problems because this file is a configuration file. How is this possible? Why aren't some clients taking affect and some are? TIA
On Sun, Nov 15, 2009 at 05:04:47PM -0500, Mag Gam wrote:> At our lab we have 200 clients which are mounting to samba share. On > some clients a certain file has a different checksum than the others. > This is causing many problems because this file is a configuration > file. How is this possible? Why aren't some clients taking affect and > some are?That's bad, that should not happen. What Samba version is this, and what kinds of clients are those? Can you nail broken files to some clients? Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20091116/acc3e1e2/attachment.pgp>
how can I check what settings the client is using? I can always check the /etc/mtab but if there a way to see what type of locking mechanism my client and server are using? On Mon, Nov 16, 2009 at 8:09 AM, Volker Lendecke <Volker.Lendecke at sernet.de> wrote:> On Mon, Nov 16, 2009 at 07:25:36AM -0500, Mag Gam wrote: >> This is from Redhat 5.2 client (Version is 3.0.28) . Its really hard >> to get what client has this problem. But it occurs to pretty much all >> of my clients. >> >> Any thoughts? > > This is using smbfs or cifs? You might want to try the > other to rule out client fs problems. > > Volker > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAksBTv4ACgkQbZMKAi3WUkmzsgCdFC40gneOMTl32kYYN5lL0evX > 4/4AnRHdIIC9taF/lFsd8ncE5Uw7rypK > =clsU > -----END PGP SIGNATURE----- > >