[Eisfair] Fehlermeldung beim Einsatz von rsync - NEU

[Marcus Roeckrath]

Hallo,

Marcus Roeckrath wrote:

>> LDD zeigt:
>> ------------------------------
>> linux-vdso.so.1 (0x00007ffc62b8d000)
>> libacl.so.1 => /lib64/libacl.so.1 (0x00007f05e5622000)
>>      ==> libz.so.1 => /lib64/libz.so.1 (0x00007f05e540b000)
>>      <=============

Im zlib-Verzeichnis von rsync finden sich explizite Anmerkungen zur Nutzung
einer externen libz:

"READ THIS BEFORE TRYING TO DYNAMICALLY LINK RSYNC AND ZLIB!

zlib has been adapted slightly for use in rsync. Please don't bother
the zlib authors with problems related to the use of zlib in rsync as
any bugs are likely to be our fault and not theirs.

Specific changes that have been made to zlib for rsync include:

- add Z_INSERT_ONLY to allow for efficient history updating without
  actually emitting any data. This is used to compress the matched
  blocks that don't cross the wire, which gives better compression
  ratios on the literal data.

- fixed a number of minor compilation issues. (redefinition of MAX and
  other such trivial things)

- include rsync.h to ensure that we get a consistent set of includes
  for all C code in rsync and to take advantage of autoconf

As a result of the first item, the streams from rsync's version of
zlib are *not compatible* with those produced by the upstream version
of rsync.  In other words, if you link rsync against your system's
copy, it will not be able to interoperate with any other version if
the -z option is used.  (Sorry.  Sometimes standard is better than
better.)
                                                                       
The rsync maintainers hope to fix this problem in the future by either 
merging our changes into the upstream version, or backing them out of  
rsync in a way that preserves wire compatibility.  But in the meantime
this version must be maintained in parallel."

Also:

1. Die rsync-Version der libz ist gegenüber dem Original gepatcht.

2. Es können nur rsync-Versionen miteinander kommunizieren, die auf gleiche
Weise die libz benutzen, also intern oder extern gelinkt.

3. Die rsync-Maintainer hoffen, dass ihre Patches in die offizielle libz
Eingang finden.


Das bringt uns der Lösung des Problems auch nicht näher, aber es ist bislang
alleine die SuSE, die rsync gegen eine externe libz linkt, andere Distris
tun dies nicht und haben möglicherweise Gründe dafür.

Falls sich damit das Problem auch bei Jürgen löst, sollten wir vorläufig bei
der Variante mit internem libz bleiben.

-- 
Gruss Marcus