backuppc / cygwin-rsyncd Goto Github PK

For your consideration... A github action to build the installer, create a release and attach it when you create v* tags.

# .github/workflows/release.yml
on:
  push:
    tags:
      - 'v*'

jobs:
  build:
    runs-on: ubuntu-20.04
    steps:
      - name: Checkout Code
        uses: actions/checkout@v2
      - name: Install NSIS
        run: sudo apt update && sudo apt install -y nsis
      - name: Build Installer
        run: makensis -V4 backuppc_rsync-server.nsi
      - name: Create Release
        uses: actions/create-release@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          tag_name: ${{ github.ref }}
          release_name: Release ${{ github.ref }}
          draft: false
          prerelease: false
      - name: Upload Release Asset
        id: upload-release-asset
        uses: actions/upload-release-asset@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          upload_url: ${{ steps.create_release.outputs.upload_url }}
          asset_path: ./*.exe
          asset_name: installer.exe
          asset_content_type: application/vnd.microsoft.portable-executable

Not the normal use case. It looks like BackupPC on CentOS 7 x64 is able to communicate with older versions. I've installed 32-bit 3.0.9.0 from SourceForge on an older PC and that works fine for BackupPC.

The problem arises when I use the latest rsync client here (3.2.3.1 x64) to access that 32-bit server. My objective is to move some user data and profiles from an old machine to a new one. I see this:

C:> c:\rsyncd\bin\rsync.exe pippin::C/
rsync: on remote machine: --no-msgs2stderr: unknown option
rsync error: requested action not supported (code 4) at /home/lapo/package/rsync-3.0.9-1/src/rsync-3.0.9/clientserver.c(849) [sender=3.0.9]
rsync: [Receiver] read error: Connection reset by peer (104)
rsync error: error in socket IO (code 10) at io.c(784) [Receiver=3.2.4dev-no-msgs2stderr]

I saw that there's no 64-bit version of the latest release: #1

Trying to install latest cygwin-rsyncd-3.2.3.1 i got a McAfee warning about an Artemis infection.

Virustotal confirms the same.

https://www.virustotal.com/gui/file/2b3bfeb2f2edce37a5cebe52e30a01cb42f0c9cb491f06442d33fef929f6489f/detection

Hi,

Conf:
cygwin-rsyncd: 4.1.2.1 (Windows 7/10)
Debian 9
backuppc: 3.3.1-4

I have an issue with the rsyncd 4.1.2.1 and the uid and gid parameters in rsyncd.conf.

Full Backup works normally but incremental backup failed with the following errors:

server side:
2018-10-01 12:10:51 Aborting backup up after signal PIPE
2018-10-01 12:10:54 Got fatal error during xfer (aborted by signal=PIPE)

Client side:
...
rsync: setuid 0 failed: Invalid argument (22)
....
rsync error socket io code 10
Connection reset by peer (104)

Every thing works perfectly with cygwin-rsyncd 3.0.9

Regards,

Please add this file to repo - it will make life easier for many users.

Should the path setting in the commented out [docs] example in the distributed rsyncd.conf be changed? I followed its lead when creating a [users] share since that's all I'm backing up and set path = c:/Users initially. It took me an embarrassingly long time to figure out I needed to change that to path = /cygdrive/c/Users. I wonder if I'm not the only noob to get tripped up by this.

Software

Release: cygwin-rsyncd-3.2.3.0
OS: Microsoft Windows 10 Pro (10.0.19041 Build 19041)

Problem Description

After running the cygwin-rsyncd installer, the RsyncServer service fails to start. Attempting to manually start the service also fail. It looks like A cygwin DLL is missing. From C:\rsyncd\rsyncd-stderr:

C:/rsyncd/bin/rsync.exe: error while loading shared libraries: cygxxhash-0.dll: cannot open shared object file: No such file or directory

4 workstations- 3 are 64 bit and 3.1.2.0 and 3.1.2.1 both install ok
One 32 bit workstation , the rsync service is not being created. A check of the rsync file in /bin says that is is the wrong type. (64 bit) and will not run on the 32 bit computer.
Installer is very fast and I cannot get the output from the "Show Details"
If there is a install log, I will provide if you can tell me where it is located.
The 32 bit workstation, I could not get 3.1.2.0 to install either, I have reverted back and still running 3.0.9.0 and deleted the blat stuff as it was triggering the antivirus.

The powershell command to create a suitable firewall is below in case there's any way to run something like this in the installer. Would be nifty to prompt for an optional IP and add -RemoteAddress x.x.x.x too.

New-NetFirewallRule -DisplayName "Allow Inbound TCP 873 for RSYNCD" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 873 -Program C:\rsyncd\bin\rsync.exe -Profile Domain,Private

First of all: thanks for packaging rsync ready to use, makes my life much easier.

I am running rsync on the family PCs around, but some long backups abort since the PCs enter sleep before completing the backup. So I was wondering if there is a way to keep windows from entering standby or hibernation while transfers are happening.

Looking around I found the cygwin nosleep package, which uses Windows' API to set the power requirements for the thread (https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-setthreadexecutionstate).

According to Microsoft's documentation:

To run properly on a power-managed computer, applications such as fax servers, answering machines, backup agents, and network management applications must use both ES_SYSTEM_REQUIRED and ES_CONTINUOUS when they process events.

Would you think this could be patched into rsync, so that it prevents the PC from sleeping while a client is connected?