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.

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

Use cygdrive prefix for secrets file path. #9

Merged
merged 1 commit into from
Feb 13, 2021

Conversation

ossama-othman
Copy link
Contributor

BackupPC server attempts to access client modules listed in the sample
rsyncd.conf file shipped with cygwin-rsyncd will be denied because of
the use of native Windows paths in the secrets file configuration,
e.g. c:/rsyncd/rsyncd.secrets, presumably because the RsyncServer
process can't find the file. Using the "cygdrive" prefix in the path,
i.e. /cygdrive/c/rsyncd/rsyncd.secrets, allows module access to
succeed.

BackupPC server attempts to access client modules listed in the sample
rsyncd.conf file shipped with cygwin-rsyncd will be denied because of
the use of native Windows paths in the secrets file configuration,
e.g. c:/rsyncd/rsyncd.secrets, presumably because the RsyncServer
process can't find the file.  Using the "cygdrive" prefix in the path,
i.e. /cygdrive/c/rsyncd/rsyncd.secrets, allows module access to
succeed.
@ossama-othman
Copy link
Contributor Author

According to the Cygwin documentation use of native Windows paths is inadvisable, and may not necessarily work for Cygwin applications (like RsyncServer?). If native Windows paths are indeed problematic for Cygwin applications, shouldn't all of the paths in the sample rsyncd.conf use the cygdrive prefix?

At the very least, using the cygdrive prefix for my secrets file path addressed BackupPC server access to my client modules.

@craigbarratt craigbarratt merged commit be2ffa7 into backuppc:master Feb 13, 2021
@craigbarratt
Copy link
Contributor

Thanks for submitting this fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants