Red Hat Bugzilla – Bug 30772
pump does not set hostname
Last modified: 2007-04-18 12:31:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76C-CCK-MCD Netscape [en] (X11; U; SunOS 5.8 sun4u)
In redhat 7.0, if my hostname on my laptop was set to
"localhost.localdomain" the pump program would set my hostname to whatever
was proper for the current connection (be it at work or at home) to include
hostname and domainname. however, in this wolverine release, it seems to
stay as localhost??
Steps to Reproduce:
1. set hostname to localhost.localdomain
2. setup DHCP server to give me a known address
3. setup forward and reverse dns
4. boot laptop
5. login screen says "Welcome to localhost.localdomain"
Actual Results: login screen says "Welcome to localhost.localdomain"
Expected Results: login screen says "Welcome to bongohead.Central.Sun.COM"
or if at home "Welcome to bongohead.local.redneck.nu"
I have tried 'service network restart' and had limited success, but now its
not working at all.. I have added a check in the ifup script to make sure
it was working
echo $PUMPARGS > /pumpargs
and I get "--lookup-hostname"
(which is correct)
Not sure why its not working properly.
knop@sunray5:~$ nslookup bongohead
knop@sunray5:~$ nslookup 188.8.131.52
ok... here's some more stuff... then I gotta go home :)
It is now re-producable...
- Boot laptop (with network configured as before)..
- login screen says localhost
- login as root (to the console tty1) and /etc/init.d/network restart
- go back to the X screen and restart the X server (CTRL-ALT-BKSPC)
- it goes to a grey screen with a X mouse
- a little whil later gdm dies and takes the X server with it.
I presume it has something to do with the "depreciation" of nslookup.. or else
there is some sort of other name resolution problem...
I tried entering the network restart comand from within X, and could not even
I will play more with this tomorrow...
If there are any suggestions, I would be glad to try them (I work the night
Sun Microsystems - Resolution Center Americas
We've had a heckuva time reproducing defects like this here in NC. How
reproducible is this bug and would you be willing to reproduce remotely for us?
We'd REALLY like to fix this...
Created attachment 11982 [details]
pump and dhcpcd information
Please ignore last attachment.
I have a similar problem with pump. I get no hostname assigned.
However, if I move /sbin/pump so that ifup uses dhcpcd instead
I do get a hostname. But I get two dhcpcd clients started?
See following attachment
Created attachment 11983 [details]
good pump and dhcpcd information
I would have responded sooner... but it appears I do not recieve updates to this
ticket in email?? or i lost it.. whatever..
I was able to reproduce it everytime... however, right now my machine is
statically assigned and is actually bound to NIS... btw, kudos to the folks that
made all this stuff work with 32bit UID's :)
I can do whatever you want to try to reproduce it.. I just noticed that up2date
actually works in the beta release... albeit kinda slow right now, I will do a
fresh install on my laptop (to be sure all my little nis tweaks dont interfere)
and run all updates... then try it again.. and let you know. It will not be
possible for you to login to my laptop on the network.. (damn firewall) but I am
pretty handy in linux.. and can probably get you whatever you request...
Since I dont seem to be getting updates.. if you could cc TJ.McNeely@Sun.com
when you add a note it would be handy.
I do not remember how wolverine behaved but post wolverine QA releases,
including 0404 seems to set the hostname using reverse DNS, if available. If
not available, it defaults to localhost.
I thought I added this note already...
The updated PUMP package (now that update agent works again) fixes the problem..
I have verified it twice. The pump package that comes on the wolverine CD seems
to be the problem.. So long as the new pump package is released with FCS there
should be no problems.
issue is resolved by updated pump package - currently version pump-0.8.11-1
I did not encounter this problem when my client machine was running Wolverine,
but now that the DHCP server is running Seawolf it suddenly shows up. I have
two client machines; one running Wolverine, one running Seawolf. When the
server was running Guinness everything was OK, but as soon as it was upgraded to
Seawolf pump would not set the hostname. If I change to dhcpcd, however,
I am using Solaris DHCP/DNS/etc servers.. my seawolf laptop and desktop both are
obtaining hostnames correctly. and with a quick tweak to the /etc/auto.master
file, this is a totally viable desktop (it binds to NIS, mounts my home dir, and
participates like a champ :))
Sun Microsystems - RC Americas
Sounds like the bug has been fixed a long time ago - closing!