On Sun, 24 Aug 2014 15:44:26 -0400 (EDT), David Baron wrote: > On Sunday 24 August 2014 11:45:40 Stephen Powell wrote: >> ... >> Here is how I enabled it. (The following commands are >> executed as root.) >> >> cd /lib/systemd/system/multi-user.target.wants >> ln -s ../rc-local.service rc-local.service >> >> Now shutdown and reboot. /etc/rc.local will get executed this time. > > Interesting point. Mine seems to be working without this. > ...
Well, list, the joke is on me. It turns out that /etc/rc.local was being executed after all, even without adding the symbolic link mentioned above. This obviously begs the question, Why did I think it wasn't being executed? I have a static route command in my /etc/rc.local file to define a route to another network. I won't go into the reasons for why it's there. Suffice it to say that there's a reason for it. But the command is route add -net 192.168.1.4 netmask 255.255.255.252 gw 192.168.0.2 metric 2 At some point, I issued the command netstat -rn to see if my static route was there. It wasn't. I therefore concluded (erroneously, as it turned out) that /etc/rc.local had not been executed. But it had. The culprit turned out to be network-manager. The default installation of Debian for a desktop system (XFCE in my case) installs both ifupdown and network-manager. It allows ifupdown to manage only the local loopback interface (lo) and allows network-manager to manage everything else, including the wired ethernet interface (eth0). I have changed this and have given ifupdown control of the eth0 interface. But network manager insists on creating an "eth0" connection on every start-up. If I right-click on the network- manager icon, then left-click on "Edit Connections", I see two connections listed. One is "ifupdown (eth0)" and the other is simply "eth0". (I have "managed=true" in the [ifupdown] section of /etc/NetworkManager/NetworkManager.conf.) I then select the "eth0" connection and click on the "Delete" button. The connection disappears, and "ifupdown (eth0)" becomes the default connection. Everything works fine. Except for two things. (1) The stupid connection reappears on every startup. I have not found a way to prevent it from being created in the first place, and (2) deleting the "eth0" connection causes network-manager to delete the static route that I have in my /etc/rc.local file. And that is why I thought that /etc/rc.local had not been executed. I hate network-manager! Is there anything I can do to make it leave eth0 totally in the control of ifupdown and to not touch it at all, and to not create a stupid extra connection, and to leave my static routes, that it did not create, alone? -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1496131881.406849.1408917652680.javamail.r...@md01.wow.synacor.com
