> Is the tempdir in coda? If there is a conflict, mv probably fails to > rename the object and falls back on copy/unlink, and the unlink will > fail as well. > > So the next time around the conflicts in the temp directory are still there.
Except that no, the tempdir is not in coda. It is in /tmp. So the
script really looks something like this:
/bin/rm -rf $codadir/update.last
/bin/mv $codadir/update $codadir/update.last
/bin/mv /tmp/$subdir $codadir/update
And right now a quick find command shows that the faux conflicts are in
both the update directory and the update.last directory. Example:
# find . -lname '@*'
update/remupd/ilog.ppi
update.last/remupd/ilog.ppi
# ls -l update/remupd/ilog.ppi
lrwxr-xr-x 1 hacluste 65534 36 Jul 13 14:40
update/remupd/ilog.ppi -> @[EMAIL PROTECTED]
# ls -l update.last/remupd/ilog.ppi
lrwxr-xr-x 1 root 65534 36 Jul 13 14:10
update.last/remupd/ilog.ppi -> @[EMAIL PROTECTED]
It's interesting to note that the broken link is the same in both
places. Obviously whatever is going wrong happens on the initial mv
from /tmp to /coda and then the problem percolates to the update.last
directory.
--
Patrick Walsh
eSoft Incorporated
303.444.1600 x3350
http://www.esoft.com/
signature.asc
Description: This is a digitally signed message part
