Can we make this bug public ? customer is requesting for public access .
(In reply to mpathan from comment #3)
> Can we make this bug public ? customer is requesting for public access .
I am fine with that.
Also if you don't want any networking daemon running on background I think that NM now has some set&exit mode.
Created attachment 1185085 [details]
Suggestion to fix this issue
As I wrote in comment #1 I am sorry, but we don't accept any new features to initscripts. Please try NetworkManager instead and file any RFE there.
The attached patch is just for reference. Maybe other people have similar issues and the patch could help them.
I'm reopening this BZ so it is reconsidered as a valid request for enhancement for initscripts package.
IMHO, even though the 'initscripts/network-scripts' are in "deprecated" state, I think this request is reasonable enough to at least try to implement this change.
However, I can only suggest to add support for 'DNS3' option, because glibc's MAXNS value is still (even in Fedora) set to value *3*, meaning that only 3 nameservers will be actually used for name resolving.
ATM I don't see a valid reason to support DNS4 (or more) in network-scripts, especially when network-scripts are already in "deprecated" state, and they were never meant to be 1:1 equivalent to NetworkManager in the first place. (NetworkManager is suppose to replace and surpass the limitations of network-scripts.)
-- David --
Pull-request submitted into upstream:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.