On those distribution, Linuxconf is using internal rules to find out what has to be started,restarted,stopped or reconfigured.
Since these rules are limited (fixed), this only works for a limited services set.
Sysv init scripts on those distribution can nevertheless be enhanced (see below) and Linuxconf will probe those scripts. But Linuxconf internal rules take precedence.
Currently, only RedHat derivative fits are aware. These distributions are based on sysv init scripts.
Linuxconf relies on tags in the sysv init scripts. You can find
documentation about those tags at
The network script (/etc/rc.d/init.d) is a little special. For the network script, it uses the tag "probe: true". This tells Linuxconf to let the script finds out by itself if it needs a restart or not (restart of whatever). When probe is true, Linuxconf calls the script with the probe argument
this normally prints nothing when everything is up to date. If something is not right, the script output simply "reload". Linuxconf picks this string and if you choose to activate the changes, it calls the script with this string.
Now, finding out if something has to reconfigured is not trivial, so the network script is using specials Linuxconf command lines to find out. They are: