Monday, March 15, 2004
MS Office Files getting set to read-only when edited on a Samba share.
A problem cropped up this morning when some home directories were migrated to a new server. Two users reported problems with Excel and Word files crashing. We narrowed it down to files edited and saved by MS Office 2000. The same files edited in OpenOffice didn't have the problem. After saving the files, the permission mask got set to -r--------.
It was odd, because the problem was easy to reproduce on this server, but not on the original host of the home directories, which had an identical smb.conf.
Turns out that the new server had an rpm isntalled of Samba 2.2.7 , where our other servers had a locally compiled version of 2.2.8
When running testparm on the two installations, the newer install offered this parameter-
...set to null, apprently, but it did make a difference. When I installed 2.2.8 on the problem server, it fixed the error.
This recent samba list thread seems to report a similar problem, though the workarounds are done by forcing the mask-
http://lists.samba.org/archive/samba/2004-March/081690.html
We don't force many permissons on our shares. Here's the config of the share that had the problem.
A problem cropped up this morning when some home directories were migrated to a new server. Two users reported problems with Excel and Word files crashing. We narrowed it down to files edited and saved by MS Office 2000. The same files edited in OpenOffice didn't have the problem. After saving the files, the permission mask got set to -r--------.
It was odd, because the problem was easy to reproduce on this server, but not on the original host of the home directories, which had an identical smb.conf.
Turns out that the new server had an rpm isntalled of Samba 2.2.7 , where our other servers had a locally compiled version of 2.2.8
When running testparm on the two installations, the newer install offered this parameter-
acl compatibility =
...set to null, apprently, but it did make a difference. When I installed 2.2.8 on the problem server, it fixed the error.
This recent samba list thread seems to report a similar problem, though the workarounds are done by forcing the mask-
http://lists.samba.org/archive/samba/2004-March/081690.html
We don't force many permissons on our shares. Here's the config of the share that had the problem.
[home6]
comment = Home Folders
path = /slot1/p1/nickhome6
read only = No
create mask = 0770
profile acls = Yes
