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
relative path ^pathname starts with a slash !? #364
Comments
For the record, to workaround my issue, I simply added add "." in front of the variable... |
Its still confusing I suppose. |
I am having the same issue.. when deleting in source I get this Mon May 30 16:42:38 2016 Normal: Deleting list where permission denied because there is a double slash between the target and the file name. if I restart the service they will get in sync.. for me its like a bug.. did you got any solution on this jtognazzi ? |
whatever your issue is, I doubt it is the double // This shouldn't hurt try |
I suppose you're using default.rsyncssh not default.rsync and your rsync channel works, but your ssh channel doesn't. Easiest solution is to use plain default.rsync. |
well "onDelete" I get /home/ubuntu/target//hola.txt but when restart the deamon I get sending incremental file list is there a way to strip the // into / so I make sure this is not the issue? thanks |
and yes I am using default.rsyncssh .. let me try using srync and change the path to a remote server and see if it does it |
The double slash is 99.9% sure not the issue Try running as user Lsyncd is running with "ssh [target] touch x" |
well I gave a shot on not using the syncssh and use the default and it works as as charm here is my final setting to share in case someone uses amazon ec2 and needs to use file authentication settings {
} sync {
|
This has been changed with Lsyncd 2.2.0 |
With the rpm version 2.1.5 from epel6, I have the following behaviour:
Relative path starts with a slash
Absolute path have a double slash after the source or target directory.
Is it a bug or am I doing something wrong ?
lsyncd.conf
and this is the log i get:
lsyncd.log
The text was updated successfully, but these errors were encountered: