 |
 |
Hi Gregory, yes, you can. Just have a look at the README_params file to find a description of the parameters. To change them at runtime you have to add something like: EnvPutInt( NAME_CONNECTTIMEOUT , 15); in your code BEFORE the ctor of your XrdClient objects gets invoked. Many parameters are read only inside the ctor. Fabrizio On Friday 12 August 2005 04:13 pm, Gregory J. Sharp wrote: > We have written the necessary backends for Suez to get data from > xrootd and they seem to work okay. However, we cannot profile our > code or look for memory leaks because valgrind and purify slow > everything down to the point that we get timeouts communicating with > xrootd. > > Is it possible to get an interface via XrdClientConn that will let us > set the default timeouts a little longer when we run valgrind? Or is > there some other profiling tool that lets us get the info we need to > check our code for memory leaks without slowing it to the point of > timeouts? > > -- > Gregory J. Sharp email: [log in to unmask] > Wilson Synchrotron Laboratory url: http://www.lepp.cornell.edu/ > ~gregor > Cornell University ph: +1 607 255 4882 > Ithaca, NY 14853 fax: +1 607 255 8062