[SOLVED] Network init scripts

xflow7 · 08-29-2012, 07:27 PM

A couple of other threads got me thinking about this.

In rc.d there exist rc.inet1, rc.networkmanager, and (potentially) rc.wicd all of which in a broad sense do network interface stuff.

My question is, if a user is using, say rc.networkmanager, then presumably rc.wicd should be chmod 644 and vice versa. This appears to be borne out by the logic in rc.M.

However, when using either rc.networkmanager or rc.wicd, should/could rc.inet1 also be disabled?

Thanks,

Dave

yenn · 08-29-2012, 08:16 PM

Quote:

Originally Posted by xflow7

My question is, if a user is using, say rc.networkmanager, then presumably rc.wicd should be chmod 644 and vice versa. This appears to be borne out by the logic in rc.M.

If you want to keep both installed, like I prefer wicd, but keep along NetworkManager because it simplifies VPN connection, then disable execution for the one you don't use regularly. Otherwise I'd suggest uninstalling the one you don't use.

Quote:

Originally Posted by xflow7

However, when using either rc.networkmanager or rc.wicd, should/could rc.inet1 also be disabled?

You definitely shouldn't. rc.inet1 activates network interfaces defined in /etc/rc.d/rc.inet1.conf and set default route (if defined in rc.inet1.conf). Unless you want to disable networking, don't disable this script.

elvis4526 · 08-29-2012, 08:17 PM

Normally, NetworkManager and wicd do everything that rc.inet1 do, so yes, it can be disabled if you use networkmanager or wicd.
venn: Are you sure about that?

Didier Spaier · 08-29-2012, 11:03 PM

@elvis4526: everything, but bringing up a loopback interface.

I can't say a word about NetworkManager which I didn't use yet, but for wicd there is no problem with rc.inet1 staying executable, provided that rc.inet1.conf stay or be brought back to its initial state, i.e. with no line uncommented in it.

mrascii · 08-30-2012, 12:43 AM

I've not touched /etc/rc.d/rc.inet1 since I started using NetworkManager and everything works fine.

DNA
AKA mrascii

xflow7 · 08-30-2012, 06:18 AM

Thanks all for the responses.

I hadn't seen any problems having both rc.inet1 (with default rc.inet1.conf) and rc.networkmanager running. I was more just interested in what was considered best practice and/or if there was an opportunity to eliminate redundant execution at boot.

Interestingly, I've just experimented with disabling rc.inet1 (chmod 644) and my loopback device still appears to get set up at boot:

Code:

drw1@rosberg:/etc/rc.d$ /sbin/ifconfig lo
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 16  bytes 1152 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16  bytes 1152 (1.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

In any case, marking this one as SOLVED

yenn · 08-30-2012, 09:36 AM

Quote:

Originally Posted by elvis4526

venn: Are you sure about that?

Well, now I'm sure that what I wrote isn't correct. What I meant was rc.inet1 brings up network interfaces (if defined or use DHCP) and rc.wicd or rc.networkmanager only starts it's deamons. Which in fact brings up network interaces, even if these scripts don't do the same, result is the same.

My guess is network interfaces are added by udev, at least these listed in /etc/udev/rules.d/70-persistent-net.rules. I'm not sure what brings loopback up. So, yes it's possible to disable rc.inet1, but if you use DHCP I think rc.inet1 subjectively speeds booting up to "everything-is-loaded-and-ready" state, because network connection is set up during boot before Xorg starts.

I made a fool of myself, but at least I learnt something