shame on me but I didn't save the file and probably can't easily duplicate the situation that lead to the problem as I needed to move on and change the config of the system I was trying to upload.  If this happens again, I'll be more careful about preserving state.

as far as rsync goes, all I can say is the autoinstallscript was fine on the source computer and corrupted on the target.  there were some directories that shoudn't have been on the source and after I removed them the installation worked.  however, I would have thought rsync would have still copied things as is, but this was an OpenSSI environment complete with cdsl's and perhaps there is something funky that confused rsync.

-mark

dann frazier wrote:
On Fri, Jan 16, 2004 at 06:47:11PM -0500, Mark Seger wrote:
  
Here's some more detail...  The one file I inspected on the server, 
/etc/systemconfigurator/mkautoinstallscript.conf was corrupted!  It 
contained nothing like the image on the client and appeared to have a 
lot of binary data in the beginning.
    

how big was that file?  if its on the order of 1 or 2K, can you send it as an
attachment?

  
  As it turns out the client I was 
uploading had some weirdly linked directories, but the 
mkautoinstallscript.conf was valid on it.  That leads me to say it 
sounds like a problem with rsync since that's the guy responsible for 
copying the data, but...
    

rsync is very good about data integrity - i'd probably not start there.
  

Reply via email to