[CentOS] Centos 6.4: Possible bug in system-config-network-cmd

Tue May 21 21:00:17 UTC 2013
m.roth at 5-cent.us <m.roth at 5-cent.us>

Glenn Eychaner wrote:
> I'm having a puzzling problem with system-config-network-cmd in CentOS
> 6.4. I have a workstation with a number of different grub boot
> configurations (a spare for a set of workstations, basically), each of
> which has a parameter MYHOST=<hostname>, and I am using
> system-config-network-cmd to set the boot configuration during the network
> process (using a small custom system service that runs just before network
> startup, reads the configuration name from /proc/cmdline and calls
> "system-config-network-cmd -p <configname>").
> I have properly disabled NetworkManager, and have
> /etc/sysconfig/networking/devices and .../profiles set up correctly AFAIK
> (it was all copied from a CentOS 5 machine, and the hand links were
> maintained properly as needed; such a PITA that they got rid of the very
> nice GUI for this).
> This all works great, EXCEPT that if the machine is booted a fixed-IP
> profile, the the DHCP ifcfg file also winds up in
> /etc/sysconfig/network-scripts.  So, if I have in
> profiles/dhcp/ifcfg-eth0_dhcp (with a hardlink in devices/, of course):
Hmmm... have you looked at /etc/udev/rules.d/70-persistant-net.rules?