From owner-freebsd-stable Mon Sep 18 9:17:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from penguin.prod.itd.earthlink.net (penguin.prod.itd.earthlink.net [207.217.120.134]) by hub.freebsd.org (Postfix) with ESMTP id 7C9F637B423 for ; Mon, 18 Sep 2000 09:17:43 -0700 (PDT) Received: from rod.darktech.org (ip152.cambridge2.ma.pub-ip.psi.net [38.32.112.152]) by penguin.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id JAA23752; Mon, 18 Sep 2000 09:17:41 -0700 (PDT) Received: (from eogren@localhost) by rod.darktech.org (8.10.1/8.9.3) id e8IGHe201127; Mon, 18 Sep 2000 12:17:40 -0400 (EDT) (envelope-from eogren) Date: Mon, 18 Sep 2000 12:17:40 -0400 From: Eric Ogren To: "Michael Sperber [Mr. Preprocessor]" Cc: mitayai@bricsnet.com, Freebsd-Stable Subject: Re: adduser & NIS Message-ID: <20000918121740.B1102@earthlink.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from sperber@informatik.uni-tuebingen.de on Mon, Sep 18, 2000 at 05:47:44PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Sep 18, 2000 at 05:47:44PM +0200, Michael Sperber [Mr. Preprocessor] wrote: > > Unfortunately, there's a race with yppasswdd this way. I have not > been able to find a way around it. In principle, yppasswdd performs > locking, but how it does this is undocumented, and there is no adduser > client which respects the same type of locking. Depending on the size > of your installation, it may or may not be a problem (it is here). Oops, wasn't aware of that. My NIS domain consists of exactly two (and on occasion a third) machines, so I don't have a lot of experience with large installations. Thanks for the correction. Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message