From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH v2 4/5] unbound-dhcp-leases-bridge: Initialize logging after daemonization
Date: Wed, 30 Mar 2022 09:56:34 +0000 [thread overview]
Message-ID: <20220330095635.621181-4-michael.tremer@ipfire.org> (raw)
In-Reply-To: <20220330095635.621181-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
---
config/unbound/unbound-dhcp-leases-bridge | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/config/unbound/unbound-dhcp-leases-bridge b/config/unbound/unbound-dhcp-leases-bridge
index b098d98b4..50a0e516a 100644
--- a/config/unbound/unbound-dhcp-leases-bridge
+++ b/config/unbound/unbound-dhcp-leases-bridge
@@ -615,8 +615,6 @@ if __name__ == "__main__":
elif args.verbose >= 2:
loglevel = logging.DEBUG
- setup_logging(daemon=args.daemon, loglevel=loglevel)
-
bridge = UnboundDHCPLeasesBridge(args.dhcp_leases, args.fix_leases,
args.unbound_leases, args.hosts)
@@ -627,4 +625,6 @@ if __name__ == "__main__":
}
with ctx:
+ setup_logging(daemon=args.daemon, loglevel=loglevel)
+
bridge.run()
--
2.30.2
next prev parent reply other threads:[~2022-03-30 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 9:56 [PATCH v2 1/5] unbound-dhcp-leases-bridge: Improve logging Michael Tremer
2022-03-30 9:56 ` [PATCH v2 2/5] unbound-dhcp-leases-bridge: Fix inotify handling Michael Tremer
2022-03-30 9:56 ` [PATCH v2 3/5] unbound-dhcp-leases-bridge: Read configuration only once Michael Tremer
2022-03-30 9:56 ` Michael Tremer [this message]
2022-03-30 9:56 ` [PATCH v2 5/5] unbound-dhcp-leases-bridge: Don't open stderr on daemonization Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220330095635.621181-4-michael.tremer@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox