From owner-freebsd-stable  Fri Dec 13  9:49:55 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2014E37B401
	for <stable@freebsd.org>; Fri, 13 Dec 2002 09:49:54 -0800 (PST)
Received: from support.urchin.com (support.quantified.com [63.212.171.7])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C023943EC2
	for <stable@freebsd.org>; Fri, 13 Dec 2002 09:49:53 -0800 (PST)
	(envelope-from dsilver@urchin.com)
Received: from danzig.sd.quantified.net (web.urchin.com [63.212.171.5])
	(authenticated bits=0)
	by support.urchin.com (8.12.6/8.12.6) with ESMTP id gBDHoHAm011804
	for <stable@freebsd.org>; Fri, 13 Dec 2002 09:49:56 -0801 (PST)
	(envelope-from dsilver@urchin.com)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Doug Silver <dsilver@urchin.com>
Organization: Urchin Software Corporation
Subject: Weird NIS master problem
Date: Fri, 13 Dec 2002 09:49:57 -0800
User-Agent: KMail/1.4.3
To: stable@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200212130950.19221.dsilver@urchin.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

(Originally sent to -questions, but no one replied so I'm reposting it he=
re)

I have two FBSD NIS machines, the master is running 4.6 and the slave is =
at
4.7.  The slave works properly, it's the master that is acting strangely.

The master is also serving as a router with 2 nic cards, and is running n=
tpd.
It processes NIS stuff, just *really* slowly.  It is not doing firewall s=
tuff
(yet).

For example, running 'truss id dsilver' it stalls right after running
'gettimeofday' but eventually answers back properly.  The same behavior
happens on any other client if I bind it to the master instead of the sla=
ve,
i.e. you can login, it just takes a long time.

I've confirmed that both machines are running ypserv, ypbind, rpc.statd, =
and
the server is also running rpc.ypxfrd.  Does anyone know about this stran=
ge=20
black magic known as NIS? :)

Any suggestions?

Thanks.

-Doug


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message