warnings on symlinks using link-dest

[George Georgalis]

On Sat, Feb 04, 2006 at 01:00:02PM -0800, Wayne Davison wrote:
>On Fri, Feb 03, 2006 at 10:00:27AM -0500, George Georgalis wrote:
>> rsync: symlink "/sawmill/backup/sawmill/snapshot/2006.02.03.0000.01/sawmill/home/geo/comphome" -> "/sawmill/comp/home/geo" failed: File exists (17)
>
>That's a strange error that I haven't seen before.  The "File exists"
>part of the message comes from interpreting the errno returned from a
>symlink() call, so that's what the OS is telling rsync is going wrong.
>The call that rsync tried to make is symlink($2, $1), where $2 is the
>second name mentioned in the error (the referent) and $1 is the first
>name mentioned in the error (the symlink to create).  Rsync should
>remove anything that was in the way of the symlink (which you say should
>not be there, due to the directory starting out empty).  When an error
>occurs, ls the first name and see if something is there.  Perhaps there
>is a second rsync running and the two are trying to create symlinks for
>in the same places?

You guessed it! When I brought the interval from daily to @8hr, I
forgot to remove the @24h, so every midnight....

#0 */3 * * *     /usr/local/script/backup.sh
0 */8 * * *     /usr/local/script/backup.sh
0 0 * * *       /usr/local/script/backup.sh

Thanks!
// George


-- 
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george at galis.org