From owner-freebsd-stable Wed Jun 12 0:48: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from zoon.lafn.org (zoon.lafn.org [206.117.18.9]) by hub.freebsd.org (Postfix) with ESMTP id 994D437B40B for ; Wed, 12 Jun 2002 00:48:00 -0700 (PDT) Received: from [10.0.1.90] (66-81-24-78-modem.o1.com [66.81.24.78]) by zoon.lafn.org (8.11.3/8.11.3) with ESMTP id g5C7lsG19888 for ; Wed, 12 Jun 2002 00:47:55 -0700 (PDT) (envelope-from bc979@lafn.org) Mime-Version: 1.0 X-Sender: bc979@mail.lafn.org Message-Id: In-Reply-To: <20020609201909.J7944-100000@woozle.rinet.ru> References: <20020609201909.J7944-100000@woozle.rinet.ru> Date: Wed, 12 Jun 2002 00:44:32 -0700 To: stable@FreeBSD.ORG From: Doug Hardie Subject: Re: NIS server status Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't know if this is the best place to send this, but I just encountered a problem that took a long time to diagnose. I believe the cause was ypserv terminating. It was definitely gone and when I restarted it, things worked properly again. However, ypserv, and ypbind, to not create a pid file. I have a process that periodically checks the important server pid files and makes sure the process is still allive. It then pages me if the process has died. That would be really helpful for ypserv and ypbind if they would create a pid file once they are up and running correctly. -- -- Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message