On Sat, Feb 24, 2007 at 08:37:16PM +0900, Trent Lloyd wrote:
> > Under what circumstances does this actually break for you? What does your
> > nsswitch.conf look like?
> >
> > I can understand that listing mdns first in nsswitch.conf, and mounting /usr
> > over NFS, would break as a result of this bug; but this bug severity looks
> > overinflated to me, there are pretty apparent workarounds available (i.e.,
> > don't configure nsswitch.conf in such a way that mdns is on the critical
> > path for mounting /usr).
>
> The recommended way of configuring nss-mdns which makes lookups of
> .local speedy and doesn't cause real dns to lag, also causes it
> to fail *ALL* dns lookups if you cannot find the plugin (NOTFOUND=return)
Exactly, it's the default config of libnss-mdns that breaks..
So one issue is that boot fails for nfs mounted /usr.. Another issue is that
postfix copies only the /lib/nss* modules in to it's chroot. Which you might
argue that it's a postfix bug. But it's assumption that only /lib stuff should
be enough to to dns lookups is valid imho and postfix might not be the only
daemon that assumes that.
So in the end i think it's grave because it breaks the assumption that /lib is
enough to basic dns lookups with the default/correct nsswitch setup for mdns
Sjoerd
--
The only function of economic forecasting is to make astrology look respectable.
-- John Kenneth Galbraith
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
