This is merely an explanation to the previous behaviour. Originally, we
would ignore the directive and plow on. Now we tell you that we are
ignoring the directive but still plow on.
On Tue, 20 Apr 2021, ycalas wrote:
> Hi,
>
> With XRootD version <= 4.12.3, the directive _xrd.protocol_ in the configuration file did not trigger an error when cmsd was started. It is no more the case with XRootD 5.1.1-1:
>
> `210420 14:51:08 1003972 XrdConfig: the builtin protocol is 'cms' not 'xrootd'; the following protocol directive should be corrected!
> `
>
> This problem can be solved by adding the `if-fi` conditional directives, e.g. with:
>
> ```
> if exec xrootd
> xrd.protocol xrootd *
> fi
> ```
> I am not sure if this is a bug or if this new behavior is expected though.
>
> Cheers,
>
> Yvan
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1444
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1444#issuecomment-823523055",
"url": "https://github.com/xrootd/xrootd/issues/1444#issuecomment-823523055",
"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