On Wednesday, Feb 19, 2003, at 17:59 Europe/Vienna, David Andrews wrote:
Has anyone tried using "rsync" with Sharity? When I attempt to sync the mounts on two servers I receive the message:I assume that 'fpix' is a Sharity mount, right? The error message means that creating a temporary file failed. And it seems to indicate that the error occurred on the remote side (transport endpoint). The library function mkstemp() tries to set the temporary file to particular permissions (for security reasons). This may fail with Sharity because CIFS does not support the full range of Unix permissions. There is no real fix for this, but if you don't use Sharity for other purposes, you can set the faked permissions to what mkstemp() expects. That MIGHT help...
mkstemp fpix/.a.txt.jkaar0 failed: Operation not supported on transport endpoint
I bet this can be solved through a configuration change.
Christian,That's interesting. First, I don't understand why the setup process failed, but we had a similar report months ago. That person had a broken 'sed' utility installed. Restoring it from an other machine (I think) helped. Second, Sharity should not corrupt data whatever the configuration settings are. But on the other hand, it is hard to predict what happens when parameters are completely screwed...
I have fixed the problem. As it turns out the setup process failed and a number of % variables remained in the config file. I have manually set them and the strange behaviour has disappeared. Apologies for not noticing this sooner.
Regards, Christian.
--
Dipl.-Ing. Christian Starkjohann
Objective Development
mailto:[EMAIL PROTECTED] | http://www.obdev.at/
_______________________________________________
Sharity-talk mailing list
[EMAIL PROTECTED]
To unsubscribe see http://at.obdev.at/mailman/listinfo/sharity-talk
