From fdd32f48af7993305f65989162dedd75a929966a Mon Sep 17 00:00:00 2001 From: Evgeny Vereshchagin Date: Tue, 15 Feb 2022 01:13:10 +0000 Subject: [PATCH] tests: allow running all the services with SYSTEMD_LOG_LEVEL It should make it easier to figure out what exactly services do there. For example, with SYSTEMD_LOG_LEVEL=debug userdbd (v249) prints ``` varlink-5: New incoming message: {"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{}} ``` before it crashes and systemd-resolved prints ``` varlink-21: New incoming message: {"method":"io.systemd.Resolve.ResolveAddress","parameters":{"address":[127,0,0,1],"flags":0,"ifindex":1000000,"family":0}} ``` and those messages are helpful (especially when scripts causing them aren't clever enough to keep track of random stuff they send to systemd :-)) (cherry picked from commit bf6ef6b6a9156e5f52ee69ce0c529a246f103e54) Related: #2017035 --- test/test-functions | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/test-functions b/test/test-functions index dcc893733c..a299f5ff1f 100644 --- a/test/test-functions +++ b/test/test-functions @@ -1142,6 +1142,9 @@ install_systemd() { # enable debug logging in PID1 echo LogLevel=debug >>"$initdir/etc/systemd/system.conf" + if [[ -n "$TEST_SYSTEMD_LOG_LEVEL" ]]; then + echo DefaultEnvironment=SYSTEMD_LOG_LEVEL="$TEST_SYSTEMD_LOG_LEVEL" >>"$initdir/etc/systemd/system.conf" + fi # store coredumps in journal echo Storage=journal >>"$initdir/etc/systemd/coredump.conf" # Propagate SYSTEMD_UNIT_PATH to user systemd managers