On 11/17/2012 03:21 PM, Stephen John Smoogen wrote:
On 17 November 2012 15:40, Chuck Forsberg WA7KGX N2469R <caf@xxxxxxxx> wrote:
Today's yum update changed something that caused dnsmasq to fail
to start up. Apparently dnsmasq now gets HOSTNAME from a file
anaconda creates. In the case of the omen.com server, Anaconda
did not set a hostname. Now all of a sudden dnsmasq cares about
this whereas it didn't previously.
Hi Chuck, a couple of questions
1) Which environment are you seeing this? [Fedora 17, 18 or rawhide?]
2) Did you find which magic file that dnsmasq is wanting now?
While snooping around trying to fix the problem, I discovered multiple
dnsmasq.conf files.
Anaconda should set HOSTNAME in its special file. If anaconda doesn't
get a good hostname from dhcp anaconda should ask for one!
--
Chuck Forsberg WA7KGX N2469R caf@xxxxxxxx www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
This is with 64 bit Fedora 18 - pre-beta. I jumped from F16
to the pre-beta because the most recent F16 update disabled
one of my ethernet ports.
I added HOSTNAME=omen.com to the file left by anaconda
and dnsmasq is now happy.
--
Chuck Forsberg WA7KGX N2469R caf@xxxxxxxx www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
