Oli,

Thanks for the reply.  About 1 hour after I sent my email I realized that the 
issue was not with sudo, but with SSH and as you state below, the key.  Once I 
realized this I was able to get the login working without the password :)

Now, I am seeing if I have everything else configured correctly and trying to 
do a full back up.  Fingers crossed.

Regards,
_____________________________________________
Dave Williams

On Nov 7, 2019, 3:40 AM -0500, Oliver Sieber <oli...@sieber.me>, wrote:
Dear David

Sorry for the late answer. I was quite busy. I try to write down the steps I 
did:

- In OS X System Preferences choose Sharing and  make sure you enabled remote 
login (I am pretty sure you already did this)

- I assume that you have a user backuppc on your host client. Make sure, that 
the user backuppc is able to log in by ssh without a pw. Otherwise it would not 
run.
(http://backuppc.sourceforge.net/faq/ssh.html)

- In OS X System Preferences choose Security and then the tab Privacy and  make 
sure that sshd and sshd-keygen-wrapper have full access to the hard disc. I use 
rsync only for my home folder. So eventuelly you have to add rsync to if you 
want to backup other system directories

- For rsync I installer homebrew (brew.sh). With this you can install a native 
rsync version with brew install rsync. I am not sure of backuppc works with the 
OS's native rsync.

- The images show my settings in the web frontend of backuppc


<Settings1.png>

<Settings2.png>
<Settings3.png>


I hope this helps. But I am sure that the problem is that the user backuppc 
cannot login to your machine without a key.

Best regards
Oli

Am 07.11.2019 um 03:44 schrieb David Williams 
<dwilli...@dtw-consulting.com<mailto:dwilli...@dtw-consulting.com>>:

So, I really need some help on this.  I am trying to set it up with rsync now 
instead of samba, but I am having issues.  I’ve gone through a couple of 
articles I found on the interweb but not quite there.

I have upgraded my Mac to rsync version 3.1.3, which I read you have to be on 
rsync 3.x.  I created a rsyncd.conf and I have put my 2 shares that I want to 
back up from my Mac in this file.
I also went through the ssh set up and created keys and swapped them with the 
client and server.

I also put my username in the sudoers file on my Mac.  I set it to NOPASSWD and 
also set it so that it can only use the rsync command.  So this is what I have 
in sudoers file:
dwilliams       ALL = (ALL) NOPASSWD: /usr/local/bin/rsync

When I try and test this out with the following command it is always prompting 
me for the password and I have no idea why.  Entering the password does provide 
the correct information.
ssh -l dwilliams davesmac sudo /usr/local/bin/rsync --version

I thought the line I had put in the sudoers file would ensure it would not 
prompt for a password.  What am I doing wrong and how can I get this working so 
that I can start backing up my Mac again?
Any help would be much appreciated.

Regards,
_____________________________________________
Dave Williams
Senior Oracle MDM & Financials Consultant

On Nov 1, 2019, 12:15 PM -0400, Dave Williams 
<dwilli...@dtw-consulting.com<mailto:dwilli...@dtw-consulting.com>>, wrote:
Oliver,

It’s been a long time since I had to configure backuppc.  Can you point me in 
the right direction in regards to setting up the backup with rsync over ssh?

Regards,
_____________________________________________
Dave Williams
Senior Oracle MDM & Financials Consultant
Phone: +1 954 661 8862
On Oct 17, 2019, 7:24 AM -0400, Oliver Sieber 
<oli...@sieber.me<mailto:oli...@sieber.me>>, wrote:
I would suggest to use rsync over ssh. It works pretty fine for me. I used to 
to use tar to backup the files from my mac. After the catalina upgrade it 
stopped working. Haven't found out why, since I was using gtar from Homebrew. 
Switching to rsync solved the problem.

Regards,
Oli

David Williams schrieb am 16.10.19 um 16:24:
Robert,

Thanks for that.  What commands would I need to give access to though?  I am 
connecting via smbclient from my Linux server.  Here is the SmbClientFullCmd:

$smbClientPath \\$host\$shareName $I_option -U $userName -E -N -d 1 -c tarmode\ 
full -Tc$X_option - $fileList

Regards,
_____________________________________________
Dave Williams

On Oct 16, 2019, 9:41 AM -0400, Robert Trevellyan 
<robert.trevell...@gmail.com><mailto:robert.trevell...@gmail.com>, wrote:
You probably need to make adjustments in System Preferences -> Security & 
Privacy -> Privacy -> Full Disk Access (on the client) to give the relevant 
commands the access they need.

Robert Trevellyan


On Tue, Oct 15, 2019 at 8:31 PM David Williams 
<dwilli...@dtw-consulting.com<mailto:dwilli...@dtw-consulting.com>> wrote:
I am pretty sure that this particular issue started after the upgrade to macOS 
Catalina.

My backups are now failing when it comes to backing up my Documents directory 
with the error message of chroot failed.

Can someone help me troubleshoot and get this working again.  I did a google 
search but nothing that seem applicable.

Regards,
_____________________________________________
Dave Williams

_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net<mailto:BackupPC-users@lists.sourceforge.net>
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    
http://backuppc.wiki.sourceforge.net<http://backuppc.wiki.sourceforge.net/>
Project: http://backuppc.sourceforge.net/





_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net<mailto:BackupPC-users@lists.sourceforge.net>
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    
http://backuppc.wiki.sourceforge.net<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/

Reply via email to