1 / 4

Status of Objectivity/DB on Red Hat 6.1

Status of Objectivity/DB on Red Hat 6.1. Dirk Duellmann. Objectivity/DB on RedHat 6.x. CERN is currently certifying RedHat 6.1 Objy V5.2 is only officially supported under RH5.1 & RH5.2 RedHat does not maintain compatibility with RH5.1 binaries Starting with RH6.1 they moved to glibc 2.1

dylan
Download Presentation

Status of Objectivity/DB on Red Hat 6.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of Objectivity/DB on Red Hat 6.1 Dirk Duellmann

  2. Objectivity/DB on RedHat 6.x • CERN is currently certifying RedHat 6.1 • Objy V5.2 is only officially supported under RH5.1 & RH5.2 • RedHat does not maintain compatibility with RH5.1 binaries • Starting with RH6.1 they moved to glibc 2.1 • some glibc interfaces are changed e.g. some I/O routines now use 64bit file positions • the shared library is still named libc.so.6 • Objy binaries and libs are compiled against old interface • Result: • programs compiled/linked under RH6.1 core dump because of interface mismatch • Other products which are distributed as binaries may also be affected

  3. Objectivity Plans for RH6 Support • Objectivity’s Current Plans • Objy Support for RH6.x foreseen for Objy V6 • Time frame for V6 will be discussed during the upcoming meeting at Objy (end of Feb.) • Objy is currently looking for possible workarounds • Can we wait until V6 or do we need a workaround for the meantime?

  4. A Possible Workaround ? • Problem seem to occur mainly during error messages • E.g. HepODBMS example programs work! • Some customers seem to use Objy 5.2 under RH6.1 • Objy’s default error handler uses fprintf (which core dumps) • Objy allows to replace the error handler by a user routine • Since the user handler is compiled under RH6.1 this fixes the interface mismatch • Could be hidden in the HepODBMS session class (and as a init time function for applications not using HepODBMS.) • More testing needed to exclude other interface problems • Constraint to use static objectivity libs on linux

More Related