Print

Print


Currently, the cconfig tool prints the configuration to stderr.

This is a strange behavior as it becomes difficult to work with the traditional suite of command line tools as debug messages are interspersed with the actual configuration directives.

An example:

# cconfig -c /etc/xrootd/xrootd-origin.cfg 
all.manager redirector.example.com+ 1213
xrd.port 1094
all.role server
continue /etc/xrootd/config.d
Config continuing with file /etc/xrootd/config.d/10-common-site-local.cfg ...
Config continuing with file /etc/xrootd/config.d/10-docker-env-var.cfg ...
Config continuing with file /etc/xrootd/config.d/10-origin-docker-env-var.cfg ...
Config continuing with file /etc/xrootd/config.d/10-origin-site-local.cfg ...
Config continuing with file /etc/xrootd/config.d/10-osg-xrdvoms.cfg ...
Config continuing with file /etc/xrootd/config.d/40-stash-cache-plugin.cfg ...
xrd.tcpmonlib ++ /usr/lib64/libXrdTCPStats.so 
...

Now yes, I can redirect stderr to stdout and then start grepping out known debug messages ("Config continuing with ..."). In terms of user interface, it's just strange/unexpected behavior for a Unix command line tool to use stderr for the output.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1894@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1894", "url": "https://github.com/xrootd/xrootd/issues/1894", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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