Well sometimes it's easy too. . .

Turns out that Samba is delivering inodes
that are different when the underlying file
is the same.  Have some hard-links created
in the build, and the script logic that
suppresses 'ln -f' when they're already
correctly linked was failing on the Windows
side.  This lead to brief instants when
the files really were not present.

Fixed by suppressing the re-hard-link
when 'uname -s' starts with CYGWIN_NT-.

I suppose there is some good reason why
the Samba inode values don't reflect
any semblance to the Linux reality, but
it's not helpful.



At 01:42 PM 5/9/2012 -0700, Jeremy Allison wrote:
>Well I'm sorry, but you have to understand that
>your original report is no better than "my car
>won't start - what's wrong ?".
>
>Not trying to be difficult but we need more to
>go on than you gave us.
>

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to