Description of problem:

  When files in /etc/sysconfig/network-scripts are modified, a system component is notified and updates the system configuration to match the configuration files (such as adding or removing static routes, for instance).

  This can cause problems when a system admin  logs into a remote system using secure shell and while modifying a configuration file, fat-fingers the contents such that a required static route disappears when the monitoring utility parser fails to parse the contents of the network-scripts/route-eth0 file correctly.

Version-Release number of selected component (if applicable):

  FC16

How reproducible:

  Can be reproduced at will.

Steps to Reproduce:
1. Log into console, add static route from the shell prompt using route add
   # route add -net 172.25.215.0 netmask 255.255.255.0 gw 172.25.5.95 dev eth0

2. Log into system using ssh.   Edit /etc/sysconfig/network-scripts/route-eth0
and include the above route command (note that this is not the correct format for the content of this file) and exit the editor.   As soon as the monitoring utility picks up the change to /route-eth0, the ssh connection will hang.  The situation can be recovered by logging into the console and entering the correct content in the /route-eth0 file (e.g. 172.25.215.0/24 via 172.25.5.95 dev eth0)

Actual results:

  SSH session hung until route was restored.

Expected results:

  The system configuration shouldn't automatically change when the files are modified,  a 'service network restart' should be required just as in RHEL 5,
particularly when a system is managed remotely.

Additional info: