 |
 |
Hi, The frm bug is very significant. There are other places besides NYU to use the frm between xrootd pools. Why is the fix waiting until next month? Why isn't the fix considered important enough for 3.2.2? Also what is the situation with xrdcp in extreme copy was the problem with linux threads fixed? I never got a new routine to test. Cheers, Doug On May 12, 2012, at 1:21 PM, Andrew Hanushevsky wrote: > Follow-up Comment #8, bug #94002 (project xrootd): > > Hi Attila, > > I quite understand being upset. We tried to back port the fix to 3.2.1 but we > were not successful given the time-frame we had. The web page for 3.2.0 has > the warning, > > http://xrootd.org/2012/05/11/migration_warning_3_2_x.html > > and the 3.2.1 release notes did not indicate the problem was fixed. That > said, it was our oversight to not prominently include the same warning next > to the 3.2.1 link. We will do so; though that won't help you at this point. > > The cleanest way to go back to 3.1.1 is to uninstall 3.2.1 and re-install > 3.1.1. We expect to get the next release, which should include the FRM fix, > out next month. > > _______________________________________________________ > > Reply to this item at: > > <http://savannah.cern.ch/bugs/?94002> > > _______________________________________________ > Message sent via/by LCG Savannah > http://savannah.cern.ch/ > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-DEV list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1