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

[Brian Henning]

Adding to the mix:

File ownership doesn't affect the issue.  I get the same problem 
(truncate to zero, then say I/O Error) whether it's owned by me or not.

So I'm starting to think it's not really a samba problem at all, but 
something related to KDE itself.  Especially since all of my textmode 
operations work just fine.

~Brian

Dane Miller wrote:
> 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
> 

-- 
----------------
Brian A. Henning
strutmasters.com
336.597.2397x238
----------------