Maurice Hilarius
2008-03-14 19:01:42 UTC
Good day.
We are working on a test cluster using kusu
At one point about a week ago cfmsync -p stopped working.
It failed after some updates appeared on the kusu update repository, and
not due to changes or actions on our part.
This is obviously a critical problem for us.
Some details:
This was working, until an update sometime about 7-10 days ago.
cfmsync -f DOES work.
An earlier failure of cfmsync -p was observed and that was traced to a
problem where files copied were getting time stamps in the future. Yum
simply rejected tose files.
This is a different problem, and we do not know where to start looking..
We are working on a test cluster using kusu
At one point about a week ago cfmsync -p stopped working.
It failed after some updates appeared on the kusu update repository, and
not due to changes or actions on our part.
This is obviously a critical problem for us.
Some details:
This was working, until an update sometime about 7-10 days ago.
cfmsync -f DOES work.
An earlier failure of cfmsync -p was observed and that was traced to a
problem where files copied were getting time stamps in the future. Yum
simply rejected tose files.
This is a different problem, and we do not know where to start looking..
--
With our best regards,
//Maurice W. Hilarius Telephone: 01-780-456-9771/
/Hard Data Ltd. FAX: 01-780-456-9772/
/11060 - 166 Avenue email:***@harddata.com/
/Edmonton, AB, Canada http://www.harddata.com//
/ T5X 1Y3/
/
With our best regards,
//Maurice W. Hilarius Telephone: 01-780-456-9771/
/Hard Data Ltd. FAX: 01-780-456-9772/
/11060 - 166 Avenue email:***@harddata.com/
/Edmonton, AB, Canada http://www.harddata.com//
/ T5X 1Y3/
/