Print

Print


URL:
  <http://savannah.cern.ch/bugs/?78973>

                 Summary: xproofd segfaulting in the xrootd fork handler
                 Project: XROOTD
            Submitted by: ljanyst
            Submitted on: 2011-03-03 15:28
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: ljanyst
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

++ CUT ++
On Wed, Mar 02, 2011 at 06:01:53PM -0600, Chris Jones wrote:
In our xrootd5.27.06b-cms3 version of xrootd we added a  modification from
the xrootd developers to deal with 'fork'ing. However, when xproofd does its
fork a pre-condition expected by the xrootd code does not hold and the code
tries to talk to a null C++ object. However, I think this could easily be
fixed by changing the file XrdClient/XrdClientEnv.cc such that before every
call to 'ConnectionManager' the code first does
       if( 0 != ConnectionManager ) { .... }
-- CUT --

++ CUT ++
2011/3/3 Lukasz Janyst <[log in to unmask]>:
This is one of the reasons why the final version of the patch that has made
it to the xroot repository is sligthly different that the one you got: the
fork handlers are disabled by default and one can enable them by setting an
environment flag:

  
http://xrootd.cern.ch/cgi-bin/cgit.cgi/xrootd/patch/?id=953079e8605f58f0500e6b4ed774a8ed91a75671

I can also add the check suggested by Chris just to be extra careful.
-- CUT --

++ CUT ++
2011/3/3 Peter Elmer <[log in to unmask]>:
Ok, it looks like the environment for this fix is something we can turn on
programmatically (and not via an envvar, which we don't use for
configuration), is that correct? What is the reason for making it disabled by
default? Is there a penalty for using it in the non-fork cases or is this just
"caution" because it is a new/experimental feature?
-- CUT --




    _______________________________________________________

Reply to this item at:

  <http://savannah.cern.ch/bugs/?78973>

_______________________________________________
  Message sent via/by LCG Savannah
  http://savannah.cern.ch/