Am Do den 3. Okt 2013 um 0:49 schrieb Steve Langasek:
> And how are you configuring dnsmasq?
Just as a primary DNS server for that node.
> If you are using the stock Ubuntu desktop, you will have
> NetworkManager depending on the dnsmasq-base package, and providing a
> dnsmasq server that guaranteeably starts before NM signals mountall.
Well, I see no sense for dnsmasq to run on a desktop. And I see no sense
for networmanager to run on a server.
> If you are using dnsmasq some other way - for instance, by not
> providing any fallback DNS servers to resolvconf that would be usable
> by the system between the time the network interface comes up and the
> time dnsmasq starts
Well, dnsmasq _is_ a DNS server and it is usually the primary one.
Adding more DNS servers to the resolv.conf makes your server depending
on systems you do not want them depending on.
> - then sure, that's not going to work.
It should as with other DNS servers too that are installed on the system
itself.
> But that's nota bug in mountall; mountall has no way of knowing
> that the network isn't really up yet when it's supposed to be.
mountall is a essential part of the system; as is DNS. It is easily
possible with a normal system-V system to build this dependency. If it
is not with upstart ... However, I am not a expert of upstart so it
might be possibly with it too.
Network without a running DNS resolution is not "up"; logically.
> If anything, that would be a bug in the dnsmasq package for not
> integrating properly with mountall.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
thanks for addressing this problem.
Am Do den 3. Okt 2013 um 0:49 schrieb Steve Langasek:
> And how are you configuring dnsmasq?
Just as a primary DNS server for that node.
> If you are using the stock Ubuntu desktop, you will have
> NetworkManager depending on the dnsmasq-base package, and providing a
> dnsmasq server that guaranteeably starts before NM signals mountall.
Well, I see no sense for dnsmasq to run on a desktop. And I see no sense
for networmanager to run on a server.
> If you are using dnsmasq some other way - for instance, by not
> providing any fallback DNS servers to resolvconf that would be usable
> by the system between the time the network interface comes up and the
> time dnsmasq starts
Well, dnsmasq _is_ a DNS server and it is usually the primary one.
Adding more DNS servers to the resolv.conf makes your server depending
on systems you do not want them depending on.
> - then sure, that's not going to work.
It should as with other DNS servers too that are installed on the system
itself.
> But that's nota bug in mountall; mountall has no way of knowing
> that the network isn't really up yet when it's supposed to be.
mountall is a essential part of the system; as is DNS. It is easily
possible with a normal system-V system to build this dependency. If it
is not with upstart ... However, I am not a expert of upstart so it
might be possibly with it too.
Network without a running DNS resolution is not "up"; logically.
> If anything, that would be a bug in the dnsmasq package for not
> integrating properly with mountall.
I do not understand this sentence.
Regards www.ethgen. ch/
Klaus Ethgen
- --
Klaus Ethgen http://
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <email address hidden>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQGcBAEBCgAGBQJ SUrtIAAoJEKZ8Cr GAGfasRQwMAIL9F Wl68I8imVuESSbJ aiP9 1CYWuKSk1vAZIeC whlZsf4Z0kYMEsq +tc9kgnvY/ V0qr/rake 5ioUI9yR8RwaN1f HvANIVUFy6HTrjg ypJ100PfZ0EatzX wLOT yMoHvy4z0ASh4+ sohdnHaSrMisGTO 8oE6qQ+ RX8dX8KJfKDeu ck54QZ0dCelAdfl kRP/Euv1zm3Yp7U Tu4gHktsf8SNi+ gcWzT efuFKzYpGZH3VxE Q2OKa1rkvdvOBTn OPT3vDmIM8Au5T6 ltWM9uKI4yz TNJMbTyxwpYZCP4 ju5i+g3COjsXGRd unkozIPZVeGFd/ XY3E/ imNl4oTeUahlwfF gEl/5YMelj3kFgQ A7G0VwJhJAzdkdO K3MAiNod/ mgnUonYOA/ nAzl+gSiENqs57w 8g==
H1OS4CX9bvOOhzR
mXRB+2a68iXGMAy
CUVDs22i2hAHeUO
GMH3wt6zTzqlNDG
Q5oclI6/
TI0w39BIQ5mrJnw
GQS11hS08/
YK1fC1P5mGknVIH
=PMAV
-----END PGP SIGNATURE-----