Re: --link-dest isn't linking

On 04/23, Paul Slootman wrote: > On Sun 22 Apr 2012, dar...@chaosreigns.com wrote: > > > rsync -Ha --link-dest=/media/4tb/bak/panic-2012-01-01 > > /media/2tb/bak/panic-2012-02-01 /media/4tb/bak/ > > > > root@dancer:/media/4tb/bak# ls -l panic*/home/darxus/000

--link-dest isn't linking

rsync -Ha --link-dest=/media/4tb/bak/panic-2012-01-01 /media/2tb/bak/panic-2012-02-01 /media/4tb/bak/ root@dancer:/media/4tb/bak# ls -l panic*/home/darxus/_latest.jpg -rw--- 15 darxus darxus 100772 1999-09-14 21:19 panic-2011-12-20/home/darxus/_latest.jpg -rw--- 15 darxus darxus

Re: Writing to the wrong directory

"created directory /media/2tb/bak/da" The cron job was too long and truncated. I guess last time it truncated at "/media/2tb/" Any guesses on where the command length limit is? Cron? bash? It sure would be nice for cron to spit out an error if I create a job that's too long. -- "I don't wan

Writing to the wrong directory

I expect this is user error, but I thought I'd post in case anyone else is feeling a similar sense of losing their mind. I have a root cron job: 0 3 * * * rsync -Hva --stats --del ... / /media/2tb/bak/dancer-`date +\%F`/ "..." represents 4 --link-dest's and 22 --exclude's (including /media/)

Re: apache log backups

On 01/09, Wayne Davison wrote: > > example, www.chaosreigns.com-access.log.196.gz on the origin is the same > > file as www.chaosreigns.com-access.log.186.gz on the destination, so > The --fuzzy option might help, but only if the filenames that moved > don't already exist. Rsync expects that an e

apache log backups

I'm watching my backup via rsync, throttled to a very low speed. Looks like downloading apache logs is taking the longest time (when I'm rsyncing over an old copy of the same data) because it's not noticing that, for example, www.chaosreigns.com-access.log.196.gz on the origin is the same file as

Re: rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/

On 10/24, jw schultz wrote: > No. > > Use ssh to set up port forwarding. If you know not how, use > the ssh resources. I can't because of firewalls. workstation can connect to port 22 on both host1 and host2. host1 cannot connect to any ports on either workstation or host2. host2 cannot conne

Re: rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/

On 10/24, pod wrote: > If you are able to make ssh connections from host1 to home then the method > outlined in No, sorry for omitting that information, but the two remote hosts cannot connect to the "home" machine (my workstation, and I doubt necessary connections are allowed involving any other

rsync -vae ssh user@host1:/tmp/dir user@host2:/tmp/

I have legitimate ssh access to two remote machines. ssh directly from either machine to the other is blocked by firewalls which I cannot control. $ rsync -vae ssh [EMAIL PROTECTED]:/tmp/dir [EMAIL PROTECTED]:/tmp/ receiving file list ... done rsync: mkdir [EMAIL PROTECTED]:/tmp: No such file or