On Sat, 15 Apr 2017 14:20:47 -0700 benjamin barber <[email protected]> dijo:
>regarding rsync, you should be able to rsync to the system over ssh, i >dont think that nfs would work because of permissions, due to security >problems inherent in NFS. NFS used to work, but when I replaced the drives for volume1 the volume went away and I had to recreate it. Now I can't get the permissions right. To repeat, here is the line from fstab that used to mount the old volume (note that it uses nfs): 192.168.1.115:/volume1/Synology /media/jjj/Synology nfs auto,user 0 0 Here is my rsync command that is set to run every day at 2am: $ rsync -rptog --delete --exclude-from=/media/jjj/Movies/rsync_exclusions /media/jjj/Movies/ /media/jjj/Synology I noticed that when I use Thunar to 'Browse Network' it mounts it with smb (apparently). The location bar in Thunar says: smb://synology.local/synology/ I don't care how it gets mounted, I just want it mounted. When I click on it in the Devices list in Thunar I get mount.nfs: access denied by server while mounting 192.168.1.115:/volume1/Synology And when I try to mount it from the command line with 'sudo mount -a' I get exactly the same error message. I assume that clicking on it in Thunar is doing the same as the mount -a command, hence the same error message. It seems to me that 'mount -a' tries to mount according to the line in fstab, so maybe the solution is just to edit that line. In fact, I commented out the line in fstab, then tried 'sudo mount -a' again, and the command executed without error. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
