For an rsyncd client, the "rsync $host::" suggestion seems like an excellent idea. Its exit status appears to be correct (0 on success), and as you point out it is confirming the desired service is actually available.
Craig On Sat, Aug 10, 2019 at 6:07 PM Kenneth Porter <sh...@sewingwitch.com> wrote: > On 8/10/2019 9:50 AM, Alexander Kobel wrote: > > IMHO the only reason why one might want to replace the ping command is > > hosts that don't reply to pings for security reasons > > I'm thinking that "rsync $host::" would be a good substitute for an > rsyncd backup because it preloads the executable on the client into its > disk cache and verifies that the service, not the host, is up and > accessible. > > I set up a new Win10 client the other day and forgot to open the > firewall to ping when I opened it to rsync.exe. I mostly work from home > so fixing that means I have to coordinate with the user to meet him when > he's at the office and not busy using the host. It's just easier to > change the ping setting. And, since Windows defaults to disallowing > ping, perhaps this change is a good choice for all Windows rsyncd clients. > > > > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
