 |
 |
The maximum output can be had by start the server with the '-d' command line option. Otherwise, you would need to add a 'xxx.trace all debug' directive (substituting for xxx each possible plugin identifier). Alternatively, you can set the XRDDEBUG envar prior to starting the server which will enable debugging output for all components other than he protocol driver (which usually whose output is no necessary). On Fri, 23 Aug 2019, Albert Rossi wrote: > Is there a way to get more debug logging info from the server than what is printed using -d 3 ? > > > Thanks, Al > > > ________________________________________________ > Albert L. Rossi > Application Developer & Systems Analyst III > Scientific Computing Division, Data Movement Development > FCC 229A > Mail Station 369 (FCC 2W) > Fermi National Accelerator Laboratory > Batavia, IL 60510 > (630) 840-3023 > > ######################################################################## > 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