Red Hat Bugzilla – Bug 169366
named -v does not work.
Last modified: 2007-11-30 17:07:20 EST
Description of problem:
Command "named -v" returns nothing - should be version number.
Version-Release number of selected component (if applicable):
Easily, every time.
Steps to Reproduce:
1. Just type "named -v" on terminal command line.
Nothing (no output).
Something like "BIND 9.2.N...".
Works OK on RH EL 3 (32-bit - simulated i686 athlon, actually in a VMware VM on
Windows). Thereon returns "BIND 9.2.4rc6".
RHEL4 "man named" page still contains "-v" option.
Actually, I think you'll find this due to an SELinux issue - by default,
no network daemon with root privilege has the capability to write to any
If you do:
'Enforcing', no ?
# named -v | cat
should show the named version ?
# setenforce 0
# named -v
# setenforce 1
Should allow named to emit its version ?
This issue is fixed with the selinux-policy-targeted-1.17.30-2.110 of RHEL-4-U2.
What version of selinux-policy-targeted are you using ?
You are correct:-
getenforce = Enforcing,
named -v | cat works, as does doing setenforce 0.
rpm -q selinux-policy-targeted shows version 1.17.30-2.88.
Sorry, I am new to this aspect of RH (admin.).
My system (/etc/redhat-release file) says ES release 4 (Nahant Update 1).
I presume that you meant me to install Update 2.
I have gone to the download site for the relevant product (RH EL ES 4 AMD64).
There I see two entries. These are headed "... ES4 Update 1" and "... ES4". I
presume that the first is what I already have and the second is the original
issue of release 4. Is this correct? Is Update 2 available elsewhere or coming
Yes, RHEL-4 Update 2 will be released in the next couple of weeks.
Meanwhile, you can work around this problem by piping named output through cat.