summaryrefslogtreecommitdiff
path: root/src/veritysetup
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2018-01-24 18:01:01 +0100
committerLennart Poettering <lennart@poettering.net>2018-01-24 18:22:56 +0100
commit6c347d5024e7451336d0c5d0f7eaf90ae11d9dc9 (patch)
tree573979425305a2f337aff8f96e91eb3c42228641 /src/veritysetup
parent7a3be263d2ac9ecb17072c956789c4882c230f1e (diff)
downloadsystemd-6c347d5024e7451336d0c5d0f7eaf90ae11d9dc9.tar.gz
systemd-6c347d5024e7451336d0c5d0f7eaf90ae11d9dc9.tar.bz2
systemd-6c347d5024e7451336d0c5d0f7eaf90ae11d9dc9.zip
log: remove LOG_TARGET_SAFE pseudo log target
This removes LOG_TARGET_SAFE. It's made redundant by the new "prohibit-ipc" logging flag, as it used to have a similar effect: avoid logging to the journal/syslog, i.e. any local services in order to avoid deadlocks when we lock from PID 1 or its utility processes (such as generators). All previous users of LOG_TARGET_SAFE are switched over to the new setting. This makes things a bit safer for all, as not even the SYSTEMD_LOG_TARGET env var can be used to accidentally log to the journal anymore in these programs.
Diffstat (limited to 'src/veritysetup')
-rw-r--r--src/veritysetup/veritysetup-generator.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/veritysetup/veritysetup-generator.c b/src/veritysetup/veritysetup-generator.c
index 24bee41243..d09f295392 100644
--- a/src/veritysetup/veritysetup-generator.c
+++ b/src/veritysetup/veritysetup-generator.c
@@ -228,7 +228,8 @@ int main(int argc, char *argv[]) {
if (argc > 1)
arg_dest = argv[1];
- log_set_target(LOG_TARGET_SAFE);
+ log_set_prohibit_ipc(true);
+ log_set_target(LOG_TARGET_AUTO);
log_parse_environment();
log_open();