From owner-freebsd-questions Wed Apr 22 10:28:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27046 for freebsd-questions-outgoing; Wed, 22 Apr 1998 10:28:05 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from paris.dppl.com (exim@paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA27032 for ; Wed, 22 Apr 1998 17:28:00 GMT (envelope-from yds@ingress.com) Received: from ichiban.ingress.com (ichiban) [205.230.64.31] by paris.dppl.com with smtp (Exim 1.82 #1) id 0yS3JP-0001Kb-00; Wed, 22 Apr 1998 13:28:00 -0400 Message-ID: <013c01bd6e13$fed2e530$1f40e6cd@ichiban.ingress.com> From: "Yarema" To: Cc: "Sean Shilton" Subject: Re: ypbind w subnets Date: Wed, 22 Apr 1998 13:27:59 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ypbind -ypset > ypset master.nis.server >it returns the error of cannset set for domain nis.server on >master.nis.server, the nis clients do work after that error message >however. And when the master.nis.server is reboot the 2.2.6 clients still >hang. I get the same error message from 2.2.6R. My solution, for now is to run the "ypset master.nis.server" command from a cron job every minute or 5 minutes or whatever you prefer. a better solution is to set up a slave nis server on every subnet and not deal with the ypset silliness. so long as you're using ypset it's recommended that you start ypbind with the -ypsetme option for security reasons unless you want anybody on the net to be able to ypset your client machine to whatever server they choose. Yarema To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message