Date: Wed, 22 Apr 1998 13:27:59 -0400 From: "Yarema" <yds@ingress.com> To: <questions@FreeBSD.ORG> Cc: "Sean Shilton" <sshilton@ascend.com> Subject: Re: ypbind w subnets Message-ID: <013c01bd6e13$fed2e530$1f40e6cd@ichiban.ingress.com>
next in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?013c01bd6e13$fed2e530$1f40e6cd>