When I started this thread a week ago, I certainly did not expect this many replies. Without a doubt it seems Network Manager is a controversial topic. I still haven't worked out my Network Manager woes and just lost an hour troubleshooting a Golang webserver which wouldn't start.
Apparently in Golang's net package, there is a DNS resolver function that's called whenever a server is started. That function depends on a working /etc/resolv.conf - As per usual, the /etc/resolv.conf file turned out to be the blank template NetworkManager always creates. The webserver starts now, but this /etc/resolv.conf will certainly be blown away by NetworkManager the next time the network service restarts.
I have one idea as to why this problem persists. This file:
ll /etc/sysconfig/network-scripts/ifcfg-eth0 ...
-rw-r--r--. 1 root root 44 Apr 26 22:21 ifcfg-eth0
Is it meant to be executable? Being a configuration file, I'm assuming it doesn't need to be. Am I wrong?
On Thu, May 1, 2014 at 9:49 PM, Keith Keller < kkeller@wombat.san-francisco.ca.us> wrote:
On 2014-05-01, m.roth@5-cent.us m.roth@5-cent.us wrote:
I think I need to check with my manager - we do have a few RH licenses - and maybe I, or several of us, should put in an enhancement request for
7:
DO NOT INSTALL NM by default *EXCEPT* for either a desktop, or, better, a laptop install. DO set network up by default in all other cases.
I would suggest that it be installed and used by default for a ''beginner'' install, and specifically asked about in an ''expert'' install. I don't see the point in making a distinction between server, desktop, or laptop, because an expert setting up a laptop might prefer not to use NM, and a beginner setting up a server might need NM, or might not even know how to configure a network without it. (I know, beginners probably shouldn't be installing servers, but they're going to do it anyway.)
--keith
-- kkeller@wombat.san-francisco.ca.us
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos