Thanks for the advice. Unfortunately I tried:
--link-dest=/snapshots/rsync_test/last
and it still does not find it.
On Sun, Jan 12, 2025 at 8:37 AM Paul Slootman via rsync
wrote:
>
> On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote:
>
> > Thanks for your quick response. The rsyncd.conf file
On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote:
> Thanks for your quick response. The rsyncd.conf file looks like:
>
> charset = utf-8
> [user]
> path = /c/user
> comment = ""
> use chroot = true
Note the chroot... So "/" equals /c/user
> uid = root
> gid = root
> read only = f
On 12.01.25 03:52, Anthony LaTorre via rsync wrote:
$ rsync -aPh --link-dest=/user/snapshots/rsync_test/last
/home/user/rsync_test
rsync://admin@readynas.internal/snapshots/user/Jan_11_2025
Password:
sending incremental file list
--link-dest arg does not exist: /user/snapshots/rsync_test/last
Hi Kevin,
Thanks for your quick response. The rsyncd.conf file looks like:
charset = utf-8
[user]
path = /c/user
comment = ""
use chroot = true
uid = root
gid = root
read only = false
auth users = admin
I'm still confused about how to specify the path. The actual UNIX path is:
/c/
rsyncd doesn't take unix paths. You must adapt your --link-dest to
contend with however the rsycd module is defined in rsyncd.conf.
On 1/11/25 9:52 PM, Anthony LaTorre via rsync wrote:
Hi all,
I'm trying to figure out why a script works when using SSH but not
when using the rsync protocol. Wh
Hi all,
I'm trying to figure out why a script works when using SSH but not
when using the rsync protocol. When I run the following command:
rsync -aPh --link-dest=/user/snapshots/rsync_test/last
/home/user/rsync_test
root@readynas.internal:/user/snapshots/rsync_test/Jan_11_2025
it works perfectl
On Friday 11 December 2009 18:49:54 you wrote:
> On Fri, 2009-12-11 at 11:04 +0100, Noel David Torres Taño wrote:
> > On Friday 11 December 2009 03:43:30 you wrote:
> > > On Fri, 2009-12-11 at 01:25 +0100, Noel David Torres Taño wrote:
> > > > I don't know what I'm doing bad, but --link-dest does n
On Fri, 2009-12-11 at 11:04 +0100, Noel David Torres Taño wrote:
> On Friday 11 December 2009 03:43:30 you wrote:
> > On Fri, 2009-12-11 at 01:25 +0100, Noel David Torres Taño wrote:
> > > I don't know what I'm doing bad, but --link-dest does not work for me:
> [...]
> >
> > Pass -i to find out why
On Friday 11 December 2009 03:43:30 you wrote:
> On Fri, 2009-12-11 at 01:25 +0100, Noel David Torres Taño wrote:
> > I don't know what I'm doing bad, but --link-dest does not work for me:
[...]
>
> Pass -i to find out why rsync didn't use the file from copy1. There
> might be a difference in the
On Fri, 2009-12-11 at 01:25 +0100, Noel David Torres Taño wrote:
> I don't know what I'm doing bad, but --link-dest does not work for me:
> $ rsync -av --link-dest=$PWD/copy1 origin/ copy2
> Now I expect to see that the inode number of the kk file in copy2 is the same
> than the inode number of
Hello all:
I don't know what I'm doing bad, but --link-dest does not work for me:
I have three directories, the original one, the first copy and the second copy
I want to populate:
$ ls -li
total 12
1761433 drwxr-xr-x 2 envite envite 4096 dic 10 14:04 copy1
1761434 drwxr-xr-x 2 envite envite 40
11 matches
Mail list logo
