[TriLUG] smbfs/cifs group-write problems in KDE apps
brian at strutmasters.com
Fri May 5 11:30:40 EDT 2006
Here's a pastebin link to the group of messages appended to the log for
my client when I click the Save button in Kate.
Here's another interesting tidbit I discovered yesterday when trying to
FTP some files to a website.
Samba, on the client end, appears to be caching file contents. I can
change a file directly on the server (the way I got around the saving
problem yesterday was to forward an X session to my desktop and use Kate
directly on the server), and when I upload the "local" (as seen across
samba from my desktop) file to the webspace using gftp, what shows up on
the web does NOT reflect the changes I've just made, until I umount and
remount the samba share and re-FTP it (and yes, I'm selecting
'overwrite' in gftp).
This just started this week. I haven't seen this kind of problem
before, and this is the sort of thing I do often.
Thanks for the continued interest in helping to solve this dilemma. :-)
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
>> 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:
> log level = 3
> This is a good puzzle. Please report back with details :)
Brian A. Henning
More information about the TriLUG