From 05e4a733f2141995181a551854d5df929f084adf Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 9 Aug 2023 21:55:35 +0200 Subject: New upstream version 1.44.0 --- man/nm-cloud-setup.xml | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to 'man/nm-cloud-setup.xml') diff --git a/man/nm-cloud-setup.xml b/man/nm-cloud-setup.xml index 976fc647..74ec0400 100644 --- a/man/nm-cloud-setup.xml +++ b/man/nm-cloud-setup.xml @@ -173,7 +173,9 @@ NM_CLOUD_SETUP_LOG: control the logging verbosity. Set it to one of TRACE, DEBUG, INFO, WARN, ERR or OFF. The program - will print message on stdout and the default level is WARN. + will print message on stdout and the default level is WARN. When + run as systemd service, the log will be collected by journald can can be seen with + journalctl. NM_CLOUD_SETUP_AZURE: boolean, whether Microsoft Azure support is enabled. Defaults @@ -195,6 +197,16 @@ + + Debugging + Enable debug logging by setting NM_CLOUD_SETUP_LOG environment variable to TRACE. + In the common case where nm-cloud-setup is running as systemd service, this can be done via systemctl edit nm-cloud-setup.service + and add Environment=NM_CLOUD_SETUP_LOG=TRACE to the [Service] section. Afterwards, the log can + be found in syslog via journalctl. You may also want to enable debug logging in NetworkManager as descibed + in the DEBUGGING section in NetworkManager5 + manual. When sharing logs, it's best to share complete logs and not preemptively filter for NetworkManager or nm-cloud-setup logs. + + Example Setup for Configuring and Predeploying nm-cloud-setup -- cgit 1.3.0-6-gf8a5