Folks -
a Happy New Year to all of you, first of all!
Secondly, I wonder whether that is just me and my setup or also somebody
else is able echo that strange behaviour.
As it reproducibly now happens - I believe since OC client 2.1.0 got
installed on my Win boxes -, any newly created file on client machine A
is correctly being copied over to client machine B and C, but with the
Read-Only file attribute set.
While this is fine for the mere creation of a file, the clients on
machine B and machine C begin to choke whenever there is any change to
or deletion of a particular file on machine A - for obvious reasons.
This, BTW, also happens exactly the same way the other way round; eg.
from machine B to A and C.
Even a manual revocation of the Read-Only file attribute setting doesn't
really help: next time it gets changed remotely, it's being copied over
with a generated temporary file name - but again as Read-Only - and only
then being renamed to the correct file name: resulting in the very same
final situation.
As a quick and dirty patch a regular:
attrib -R c:\path\to\owncloud\folder\*.* /S
would do - but certainly this cannot be a permanent solution.
Again: I strongly believe this weird behaviour started with 2.1.0 - as I
never have had any problems of that kind before.
Before I file an official bug report: comments, anyone?
Best,
-C.
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
