Skip to content
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.

Sign up for GitHub

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

Jump to bottom

output / PXE / default / 82_copy_to_net.sh doesn't differentiate between rsync proto and rsync ssh #412

Closed
paianoa opened this issue May 9, 2014 · 2 comments
Closed

output / PXE / default / 82_copy_to_net.sh doesn't differentiate between rsync proto and rsync ssh #412

paianoa opened this issue May 9, 2014 · 2 comments
Assignees
@gdha
Labels
enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. won't fix / can't fix / obsolete
Milestone
ReaR future

Comments

@paianoa
Copy link

paianoa commented May 9, 2014

I would expect that OUTPUT_URL obeys the same syntax of BACKUP_URL when using rsync but it doesn't:

rsync://[USER@]HOST[:PORT]/PATH # using ssh
rsync://[USER@]HOST[:PORT]::/PATH # using rsync
@gdha gdha self-assigned this May 16, 2014
@gdha gdha added support and removed support labels May 16, 2014
@gdha
Copy link
Member

gdha commented May 16, 2014

That is correct for the the OUTPUT_URL only follows the RSYNC+SSH protocol. That might change over time, but not for now

@gdha gdha added this to the Rear future milestone Aug 21, 2014
@gdha gdha added the needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. label Jan 17, 2017
@gdha
Copy link
Member

gdha commented May 17, 2017

Solution works fine for me as it is - without contracting time we will not change it - we close the request until further notice

@gdha gdha closed this as completed May 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gdha gdha

Labels
enhancement Adaptions and new features needs sponsorship This issue will not get solved on a voluntary base by ReaR upstream. won't fix / can't fix / obsolete
Projects
None yet
Milestone
ReaR future
Development

No branches or pull requests
2 participants
@gdha @paianoa