Actually, it would still b a serious rewrite of the existing code. There
is no such concept as in-memory config files. This is further coplicated
by arbitrary if/else statements. We really looked at this in great detail
and include statements were just unworkable in the way config files are
processed. If you really need include statements you can always run the
preporcessor on your config file to create whatever config file you want
and feed the result into xrootd.
On Tue, 11 Dec 2018, Adrian Sevcenco wrote:
> well... true, if you would process in one step the statement would be complicated .. but you could do it in 2 steps : make a temporary config file (in memory or /tmp) in which you replace the include statements with the content of the respective files and _then_ process the resulting configuration file. this way you avoid the syntax modification and just add a small step at the starting of service.
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/872#issuecomment-446126156
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@abh3 in #872: Actually, it would still b a serious rewrite of the existing code. There \nis no such concept as in-memory config files. This is further coplicated \nby arbitrary if/else statements. We really looked at this in great detail \nand include statements were just unworkable in the way config files are \nprocessed. If you really need include statements you can always run the \npreporcessor on your config file to create whatever config file you want \nand feed the result into xrootd.\n\nOn Tue, 11 Dec 2018, Adrian Sevcenco wrote:\n\n\u003e well... true, if you would process in one step the statement would be complicated .. but you could do it in 2 steps : make a temporary config file (in memory or /tmp) in which you replace the include statements with the content of the respective files and _then_ process the resulting configuration file. this way you avoid the syntax modification and just add a small step at the starting of service.\n\u003e\n\u003e -- \n\u003e You are receiving this because you commented.\n\u003e Reply to this email directly or view it on GitHub:\n\u003e https://github.com/xrootd/xrootd/issues/872#issuecomment-446126156\n"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/872#issuecomment-446129764"}}}
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/872#issuecomment-446129764",
"url": "https://github.com/xrootd/xrootd/issues/872#issuecomment-446129764",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [xrootd/xrootd] Reserve `/etc/xrootd/config.d` for configuration drop-ins (#872)",
"sections": [
{
"text": "",
"activityTitle": "**Andrew Hanushevsky**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@abh3",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 872,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"xrootd/xrootd\",\n\"issueId\": 872\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/xrootd/xrootd/issues/872#issuecomment-446129764"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 422230281\n}"
}
],
"themeColor": "26292E"
}
]
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
