On Tue, Dec 11, 2012 at 9:57 PM, Balasubramaniam Natarajan wrote: > On Tue, Dec 11, 2012 at 10:08 AM, Arun Khan wrote: > >> >> I don't have your persistent rules file handy. I have not seen the >> contents change *unless* there is some hardware change - removal does >> not delete it's respective entry and addition creates an new entry >> with the eth number bumped up. >> >> > Here I did not do any hardware change all I did was "apt-get update" > followed by "apt-get upgrade" followed by "reboot", however this occured > just once. On subsequent reboots the ethX does not get bumped up by one. > > >> >> >> What Linux distro and version number? >> >> > cat /etc/debian_version > wheezy/sid >
cat /etc/issue is more general. OK - this explains it. I missed it in your OP. However, you did not mention the build date. AFAIK, Debian Wheezy is aka Testing i.e. it is not released product. Use it at your own risk. I have encountered similar behaviour [1] in Debian Wheezy and Ubuntu 12.04. Having said that, I am using Wheezy build DebianInstaller Beta3 and udev is consistent with respect to NIC devices in the persistent rules file, ditto with Ubuntu 12.04.1. [1] In my case udev would not make any entries in the persistent file after I blanked the file and rebooted the OS. > >> > This worked on an instance, thanks. However how do I make sure that the >> OS >> > does not rename the interface automatically and cause this confusion ? >> > >> >> See above - entries in the persistent rules file should not change >> mapping of eth name to mac address. You can make a backup copy of the >> persistent rules file for reference. >> >> >> > This has happened around 3 time in approximately 50 servers so far. If the > same continues I am planning to turn on the file immutable with chattr to > prevent it from getting changed, do you think that might help ? > Wheezy is in testing phase (see my above comment) - use it at your own risk. Do mention the build date if you decide to file a bug report. chattr would help (work around) but there is a more fundamental issue that you need to resolve for yourself: Will these systems be deployed into production? Sometimes it may be necessary to install Debian testing (hardware driver support) but make sure that your management is well aware of it. HTH -- Arun Khan _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
