> In article <Pine.LNX.3.96.981103234038.5588A-100000@air.fast.net>,
> "Steven N. Hirsch" <shirsch@adelphia.net> writes:
>
> > I know my configuration is correct, as it works fine with 2.1.127-pre2
> > (and as far back as I can recall). I can see some patches to the tcp code
> > for pre-3 that were introduced after pre-2. With your insight into the
> > networking layer, does anything jump out which might account for this?
>
> There is no networking change in pre3 that could explain such things.
> How exactly is it misbehaving? tcpdump? strace?
The visible symptoms are that any attempts at resolution fail with a claim
that no server is bound. ypbind does not gripe at load time, though.
I have never used tcpdump, but I did attach straces of ypbind being
started up under both 2.1.127-pre2 (the last kernel for which NIS has
worked for me) and 2.1.127-pre7.
Once up, I entered:
$ ypcat hosts
then
$ killall ypbind
Strace seems quite broken under newer kernels, but perhaps someone more
knowledgable can glean something from the information.
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/