BTW- the -m or not -m dance has come and gone with *BSD ypbind for the last 4
years.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
[EMAIL PROTECTED] said:
:- I think that there has been quite a lot of work on ypbind recently.
:- Try updating to 4.3-STABLE (actually 4.4-PRERELEASE now), there were
:- several patches in that area in the past week or two.
:- Or alternatively, wait for 4.4-RELEASE about the end of August.
Also
I think that there has been quite a lot of work on ypbind recently.
Try updating to 4.3-STABLE (actually 4.4-PRERELEASE now), there were
several patches in that area in the past week or two.
Or alternatively, wait for 4.4-RELEASE about the end of August.
G'luck,
Peter
--
Do you think anybody h
Hi:
If I'm posting to the wrong list, please let me know.
There is a long-running problem in FreeBSD's yp/ypbind that is
evidenced by:
Aug 4 02:01:43 tuva ypbind[160]: NIS server [192.32.150.15] for domain "engeast" not
responding
Aug 4 02:02:14 tuva last message repeated 30 times
Aug 4 02
4 matches
Mail list logo