[TriLUG] smbfs/cifs group-write problems in KDE apps

[Dane Miller]

Brian Henning wrote:
> group sticky is set for the folder.

Just for reference, what you're calling group sticky (chmod g+s) is
really "set group ID".  Sticky (chmod +t) is different.  'man chmod' for
the low-down.

> drwxrwsr-x 2 notme slingers 4096 May  4 10:00 grand-marquis/
> 
Nope, no sticky here.  That's too bad, I liked the simplicity of that
hypothesis.

> Aggravatingly, it effectively does delete the file, by truncating it to 
> zero size before it barfs.

Next hypothesis:  The GUI deletes the original file, then tries to save
the updated version to the original file's name with the original file's
ownership and permissions.  Since the original file was owned by
'notme', your GUI tries to set the new ownership to 'notme'.  This
throws an error because you are not notme...

But all hypothesizing aside, the right way to solve this is in the Samba
logs.  What do your Samba logs say?  It would be helpful to compare logs
for your successful vi operation against your unsuccessful GUI
operation.  You'll probably need to increase your log level in smb.conf:

   [global]
   log level = 3


This is a good puzzle.  Please report back with details :)

Dane
-- 
Dane Miller
Technology Coordinator
Olney Friends School
Barnesville, Ohio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.trilug.org/pipermail/trilug/attachments/20060505/19a9cbea/attachment.pgp>