ypbind doesn't work right on freshly installed machines
I installed two machines with fresh current snapshots last night and this morning. One was an i386 box the other a sparc64 box. Both machines are NIS clients from the same server. I do have other 5.x and 4.x boxes on the same LAN at home that also are NIS clients of the same server (the server is 4.7 box). All my other machines work fine. However, for the two freshly installed test boxs, ypbind doesn't find a server the first time it is run during /etc/rc startup. If I login as root and run 'ypbind' again then it works fine. All my other 5.x boxes which are not fresh installs do not have this problem. Anyone have any ideas? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ypbind doesn't work right on freshly installed machines
Per our discussion out-of-band, and just for the reference of others who might have the same question, forced dependencies for rpcbind from ypserv and ypbind aren't present right now, you can work around by explicitly enabling rpcbind in rc.conf. You might actually see rpcbind running later in boot, but it's from another forced dependency that is present. The symptom of this is that ypbind silently fails if the RPC port mapper isn't present :-(. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Fri, 1 Nov 2002, John Baldwin wrote: I installed two machines with fresh current snapshots last night and this morning. One was an i386 box the other a sparc64 box. Both machines are NIS clients from the same server. I do have other 5.x and 4.x boxes on the same LAN at home that also are NIS clients of the same server (the server is 4.7 box). All my other machines work fine. However, for the two freshly installed test boxs, ypbind doesn't find a server the first time it is run during /etc/rc startup. If I login as root and run 'ypbind' again then it works fine. All my other 5.x boxes which are not fresh installs do not have this problem. Anyone have any ideas? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ypbind doesn't work right on freshly installed machines
This is fixed in my WIP on rc.d . I'm more or less ready for wider review; I especially need review of the atm and diskless changes. Bill http://people.freebsd.org/~fenner/rc.d.diff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ypbind doesn't work right on freshly installed machines
BTW, /etc/rc.network never tried to save you from rpcbind_enable=NO nis_client_enable=YES so it may be a mistake for /etc/rc.d/* to try to. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ypbind doesn't work right on freshly installed machines
On Fri, Nov 01, 2002 at 04:23:02PM -0800, Bill Fenner wrote: BTW, /etc/rc.network never tried to save you from rpcbind_enable=NO nis_client_enable=YES so it may be a mistake for /etc/rc.d/* to try to. /etc/rc does though: chkdepend amd amd_enablerpcbind rpcbind_enable chkdepend amd amd_enableNFS nfs_client_enable chkdepend NFS nfs_server_enable rpcbind rpcbind_enable chkdepend NIS nis_server_enable rpcbind rpcbind_enable chkdepend NIS nis_client_enable rpcbind rpcbind_enable -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg45874/pgp0.pgp Description: PGP signature
Re: ypbind doesn't work right on freshly installed machines
Oops, you're right, I was looking too closely =) Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
