initscripts/ifup-post-fix-incorrect-condition-for-RESOLV_MODS.patch
2019-09-30 10:53:14 -04:00

33 lines
1.1 KiB
Diff

From bf6a9d7d1f708077bfaad8ea109ad8b4eeb69556 Mon Sep 17 00:00:00 2001
From: "David Kaspar [Dee'Kej]" <dkaspar@redhat.com>
Date: Mon, 20 Aug 2018 14:31:56 +0200
Subject: [PATCH 3/4] ifup-post: fix incorrect condition for RESOLV_MODS
This was causing the /etc/resolv.conf file to be always updated when
RESOLV_MODS was not set...
Before the commit 5d6156454bf8f6dab4a5fdd7e1bf6 we were not updating
the /etc/resolv.conf file if the RESOLV_MODS was empty.
See https://bugzilla.redhat.com/show_bug.cgi?id=1610411 for more info.
---
network-scripts/ifup-post | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/network-scripts/ifup-post b/network-scripts/ifup-post
index 5a89cbf3..4cb986f8 100755
--- a/network-scripts/ifup-post
+++ b/network-scripts/ifup-post
@@ -28,7 +28,7 @@ if ! is_true "$NOROUTESET"; then
fi
-if ! is_false "${PEERDNS}" || ! is_false "${RESOLV_MODS}"; then
+if ! is_false "${PEERDNS}" || is_true "${RESOLV_MODS}"; then
# Obtain the DNS entries when using PPP if necessary:
[ -n "${MS_DNS1}" ] && DNS1="${MS_DNS1}"
[ -n "${MS_DNS2}" ] && DNS2="${MS_DNS2}"
--
2.19.1