Quoting Nick Nobody ([email protected]): > > What happens when you copy the file ? > > > > I see the same behaviour than the one you see, with 3.3.3. However, > > copying the file ends up with the right permissions. > > > > I'm not entirely sure that what you see is a bug, actually. After all, > > when moving a file, you expect permissions to remain as they are. > > > > > > The same thing occurs even if I copy a file.
It doesn't on my side. Copying a file ends up with the expected permissions. Which is why I assume that experiencing the problem with "mv" only is IMHO maybe not a bug. > I'm pretty sure this is a bug, in the smb.conf manpage it says that the > mode given to the "force create mode" gets OR'd with the file's > permissions. This guarantees that you'll always have at *least* whatever > "force create mode" is set to. The way I understand this is: "create > mask" strips away permissions and "force create mode" adds them, no? If I could reproduce the bug when copying a file, I would agree. However I am not..:-) Have you considered checking the "umask" settings which you're using?
signature.asc
Description: Digital signature
