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
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
chk
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
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
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 boo
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
