<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 4, 2012 at 2:14 AM, Shlomo Solomon <span dir="ltr"><<a href="mailto:shlomo.solomon@gmail.com" target="_blank">shlomo.solomon@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It's not a lock problem (see further details below) and the other<br>
machine is also Linux.<br>
<br>
Just to be a bit clearer, if I open Kwrite on the other (Linux) machine,<br>
write some text and "save as" to the shared partition, the file is<br>
created. If I now make a change to the file and try to save, I get an<br>
error message saying I don't have permission (sorry, I don't remember<br>
the exact message and am not at the other machine right now).<br></blockquote><div><br>My bad for assuming you're using Samba to share with Windows :)<br><br>I googled for how Kwrite saves a file, and found someone who said (although that he's not sure) that Kwrite first writes the file with a new name, and when that's success, it renames the file to the old name. (myself adding: since a rename is an atomic operation, that means that you can never end up with a truncated file, even in a filesystem full situation...)<br>
<br>If that is true (sorry, going to sleep, won't be doing straces now), then you may be effectively trying to overwrite a file that is currently "open" (as per samba), which is similar to a lock.<br><br>What happens if you save a file, close kwrite, verify that the connection is dead in smbstatus, and then try to echo bla bla > filename? Does that fail to with a permission problem?<br>
<br>And again, look at the verbose logs :)<br><br>-- Shimi<br><br>P.S. If you're sharing Linux to Linux only, NFS will probably give you better performance...<br><br></div></div></div></div>