Ask Your Question

Where is NETWORKING=yes/no configured in systemd?

asked 2013-12-01 11:09:27 -0500

m8ram gravatar image

According to several bug reports I found the configuration files in /etc/sysconfig are being replaced as part of the systemd standardization (Most important bug report bug 881785).

None of the bugs I found specifically mention the NETWORKING boolean in /etc/sysconfig/network (which is still documented in Fedora 18's System Administrators Guide in D.1.13. /etc/sysconfig/network.

However on my Fedora 19 systems /etc/sysconfig contains nothing more than a comment "Created by anaconda".

I've come across a service (Logitech Media Server) that is failing because it is looking for this NETWORKING boolean in /etc/sysconfig/network.

What is the systemd counterpart to this? The closest match I found was Freedesktop's article about running services after the network is up but it doesn't answer my question.

p.s. I had to remove the links because of insuffient karma, sorry about that it makes the question less well documented, I can provide the links on request.

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2013-12-02 03:09:07 -0500

Ahmad Samir gravatar image

/etc/sysconfig/network is only relevant if you're using /etc/rc.d/init.d/network from the initscripts package; This initscript isn't used by default, NetworkManager is used instead.

You can either change that Media Server service to check the status of NetworkManager.service or something like that; or just create /etc/sysconfig/network yourself.

edit flag offensive delete link more



No, that's not true. /etc/sysconfig/network is relevant to the systemd 'network' service in exactly the same way that it was in System V. If you want to use the standard network feature, i.e. not using NetworkManager (which isn't really needed if you're on a wire and the config never changes) you can remove Network Manager (yum remove NetworkManager) and use system-config-network (yum install system-config-network) and run it to configure your network. You can then start with systemctl network on, or (as I often do) use 'service network start` which will get rerouted to the new system

cobra gravatar imagecobra ( 2013-12-02 04:17:43 -0500 )edit

network.service mainly executes /etc/rc.d/init.d/network, so /etc/sysconfig/network is only relevant if that initscript is used...

Ahmad Samir gravatar imageAhmad Samir ( 2013-12-02 07:20:04 -0500 )edit

No, again that is an incorrect statement - just read what you put. If the systemd network service is used (not NetworkManager) you may or may not be using a System V init script, but reliance on any being present is wrong and may lead to confusion as the final System V scripts are removed from Fedora. The /etc/sysconfig/network is used by the network service, which is an alternative to NetworkManager.

cobra gravatar imagecobra ( 2013-12-02 07:56:16 -0500 )edit

Right now network.service is just executing /etc/rc.d/init.d/network, which is an initscript, I don't know what'll happen in the future, but I think they won't change it not to use something else, when the SysV initscripts are totally removed they'll simply remove network.service

“The /etc/sysconfig/network is used by the network service, which is an alternative to NetworkManager.” That's what I said, maybe in other words.

Ahmad Samir gravatar imageAhmad Samir ( 2013-12-03 00:50:18 -0500 )edit

@cobra: network.service doesn't exist. It is a virtual unit systemd keeps in memory, but in reality it is exactly the network sysvinit script. See systemctl status network.service as a confirmation. Ahmad's answer is perfectly correct.

bochecha gravatar imagebochecha ( 2013-12-03 05:26:55 -0500 )edit

Question Tools

1 follower


Asked: 2013-12-01 11:09:27 -0500

Seen: 1,360 times

Last updated: Dec 02 '13