From 41b283d0f1f4abd85d0bbeeb7f71bb30f87cfab9 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 23 Feb 2018 20:46:38 +0100 Subject: [PATCH] conf-parser: let's explicitly deprecate .include in unit files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit .include lines are already deprecated somewhat, and for example explicitly not mentioned in the documentation for this reason. Let's get one step further and generatea warning when we encounter them (but still process them). Why are they deprecated? Because they are semantically awful — they complicate stat() based mtime checks for configuration files and they allow arbitrary loops we currently have zero protection against and really shouldn't have to have. --- src/shared/conf-parser.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/shared/conf-parser.c b/src/shared/conf-parser.c index 72c47150d0c..0ac63645774 100644 --- a/src/shared/conf-parser.c +++ b/src/shared/conf-parser.c @@ -211,6 +211,10 @@ static int parse_line( return 0; } + log_syntax(unit, LOG_WARNING, filename, line, 0, + ".include directives are deprecated, and support for them will be removed in a future version of systemd. " + "Please use drop-in files instead."); + fn = file_in_same_dir(filename, strstrip(l+9)); if (!fn) return -ENOMEM;