Neil Marjoram wrote:
I have just updated my DNS servers, and found that my
/etc/sysconfig/named was changed. I use the file to specify my chroot
directory, which for historical reasons is not in the default place.
It looks like the update has created an rpmnew file, but I don't
understand why the old config file was changed. Unfortunately I have
not restarted my DNS servers since last reboot (Kernel 53) so I can't
be precisly sure when the file changed. It would be nice to know what
happened as I have some very keen student hackers on site and I would
like to start eliminating causes!
Roughly speaking, rpm creates a .rpmnew file when a configuration file
changes from one version to another and when installed configuration
file has been modified.
So, in your case you edited /etc/sysconfig/named to modify the choot
directory (which is fine). Later, an update to bind(*) included a new
/etc/sysconfig/named but, because you had made that change, it didn't
just splat the fresh file over your changes, it created a .rpmnew instead.
What I do in this situation is compare the two files. I merge the
changes so that what I wind up with is basically the .rpmnew with my
changes applied to it. And then I delete the .rpmnew so that I don't
get overly confused.
And then I would line the student hackers up against the wall :-)
Does this help?
jch
(*) I believe it's the bind rpm that owns that file but I don't have an
RHEL5 system readily to hand right now to double check. check)
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
