-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
right user and group #32
Comments
I'm not sure I totally understand, but it seems like you are running oclient as the root user? If so, STOP THAT! Only run it as the user who has the files. If that's not the case, then please help me understand the issue? |
I see no reason to close this issue (yet) ... hence reopening it |
Sorry, habit on my part. @ work, whenever we are waiting for the other person/people to respond, we close the case, so that it will pop back up on the top of the stack when they respond. Habits die hard :) |
Ah ok. I have my issue list sorted by 'recently updated', doesn't that achieve the same goal? |
We don't use github @ work, we use Fogbugz, and it can definitely do that, -Craig On Mon, Apr 15, 2013 at 11:17 AM, diederikdehaas
|
Hi, I think that what faktori is saying is that there seems to be no way to choose sync files ownership and mode. Is there any system variable to fill in to setup file creation mode ? |
I'm guessing this means it doesn't honor UMASK's. I don't believe this is something the csync library supports, but I will look into it. In the meantime the answer is.. NO. sorry :( |
Does anyone know how the official owncloud client handles this? |
related issue on mirall: owncloud/client#820 |
thank you first for this client debian that meets our project.
We have a worry in the sense python cloud to the client when the sync takes place, then the client changes the group in ROOT and not its original name owncloud either:
root: owncloud to root: root
As t is a way to prevent the client exchange rights to do so.?
thks
debian6 client
server owncloud 5.03
The text was updated successfully, but these errors were encountered: