Date: Sat, 15 Feb 2020 20:40:35 -0700 From: "@lbutlr" <kremels@kreme.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: rsnapshot Message-ID: <E25A7729-CB46-4170-ADB4-F1ABF8841421@kreme.com> In-Reply-To: <3759E97D-0CDA-4503-B585-3DEA8F2E875E@kreme.com> References: <3759E97D-0CDA-4503-B585-3DEA8F2E875E@kreme.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 Feb 2020, at 19:23, @lbutlr <kremels@kreme.com> wrote: > am setting a backup from one machine to another. This is brand new = install of Rsnapshot on a brand new install of FreeBSD 12.1, the server = the is being backed up is run-in 11.4. I think I have solved this one of two possible ways. 1) Write a script on the server that rsnapshot uses instead of rsync to = launch sudo rsync. This requires passing all the usual arguments that = rsnapshot uses for rsync manually. +rsync_long_args=3D--rsync-path=3D/path/to/myrsnapscript --delete = --numeric-ids --relative --delete-excluded --exclude=3Dcore 2) allow root login in sshd.conf (Since logins require a certificate, = this is not as bad as it might seem). I went with option 1, and allow the backup user access to that one line = bash script. --=20 Light thinks it travels faster than anything but it's wrong. No matter how fast light travels it finds the darkness has always got there first, and is waiting for it. --Reaper Man
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E25A7729-CB46-4170-ADB4-F1ABF8841421>