SUMMARY: /dev/udp & ypbind client: can't get rdev

From: Rob McCauley (robmccau@RadOnc.Duke.EDU)
Date: Wed Oct 13 1999 - 13:56:11 CDT

Thanks to the following people who all came up with the identical answer:

        Jeff Woolsey <>
        Mark Baldwin <>

The solution is to add the following line to /etc/system:

        set ip:mi_maxminor = 0x3ffff

and reboot the system.

This problem has in fact already been reported to Sun and has bug ID 4209076.
A good description of exactly what is happening and how to fix it can be
found in the bug report on Sunsolve. For the sake of brevity I won't
paste it here.

I should offer the disclaimer that I haven't tried this yet as I don't
want to reboot this system at the moment. I've modified /etc/system and
will wait until a more opportune moment for the reboot. I'll post an
addendum to this summary if this doesn't fix the problem.

Thanks again!


Rob McCauley                                            Phone: (919) 681-4767
Radiation Oncology                                      Pager: (919) 970-5546
Duke University Medical Center

On Wed, 6 Oct 1999, Rob McCauley wrote:

> > I've searched the archives on this and found the question asked, but not > answered. I'll give it one more try hoping I'm giving a fairly > comprehensive definition of the problem. There *will* be a summary. :) > > I have an E450 that's exhibiting the above "ypbind client: can't get rdev" > error message. Truss revealed that fstat("/dev/udp"...) is failing with > an EOVERFLOW and a quick C test program confirms this. You can't fstat > /dev/udp on this system. I have other systems running the same rev > (Solaris 2.7 with all current required & recommended patches) that do not > display this problem. > > The primary symptom with this is that it's generating a lot of log entries. > Everything seems to work as expected, other than that the majority of my > log entries are "ypbind client: can't get rdev", which is getting logged at > LOG_DEBUG (yes, I log everything :>). I'd like to fix this short > of raising the log criteria. The fact that I can't stat /dev/udp makes > me think something is not quite as it should be. > > I did try drvconfig in hopes of regenerating the /devices entry, but this > had no effect. I'd prefer not to reboot the system for this problem. > > Any ideas or advice anyone can offer is welcome. > > Thanks! > > Rob > > -- > ------------------------------------------------------------------------------ > Rob McCauley Phone: (919) 681-4767 > Radiation Oncology Pager: (919) 970-5546 > Duke University Medical Center >

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:29 CDT