Subject: RE: Netatalk + Samba together: too many problems...
From: Jonathan Newman (jnewman@mudpup.com)
Date: Mon Nov 13 2000 - 11:52:21 EST
> > > 3) "Lock" flag (from a Mac client point of view) and "Read
> > > only" flag (from
> > > a Win client point of view) are not synchronized.
> >
> > This is a problem with Samba. Samba maintains its own
> concept of file
> > locking, avoiding the native locking mechanisms for
> speed. I believe
> > the Samba team has plans to change this.
>
> What exactly is the problem with this? We have about 20
> Macs and 10 PCs
> here, and I haven't noticed any Problems, except for the
> charset mapping
If a file is considered "locked" on windows, it still may be
manipulated by the mac. This is a real problem with any application
that maintains a "database" (I use this term loosely) on the server.
Locking is not atomic with the methods that Samba employs.
> > I thought compiling Samba with the "netatalk" option
> solved some of
> > these issues.
>
> What effect does that have exactly (we haven't noticed any
> issues with
> this so far)?
Hmmm. Well, I just looked through the Samba 2.0.7 code, and it looks
like it doesn't do anything. There are routines to maintain the
.AppleDouble information through moves/renames, but as far as I can
tell, they aren't used anywhere. :( I guess I should be more
informed before I start handing people advice.
Jon
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:37 EST