michael schuster wrote: > Adam James Wilson wrote: >> Hi Michael, >> >> I guess I downloaded the wrong distribution (this is my first time using >> Solaris); I must have assumed it was "open" because I didn't have to pay >> for it. > > I can understand. I hope it's not too much of a bother - but I guess you'll > understand we can't undermine our own business model :-) > >> I did as you suggested and tried to ping the Solaris machine after the >> "freeze;" turns out I can still ping the machine with no problem, so it >> is not a complete freeze. > > good to know. > >> Maybe I should download and install the real OpenSolaris.
Adam, Just a shot, but it's possible you ran into CR 6416641 (see http://bugs.opensolaris.org/view_bug.do?bug_id=6416641 ) at least if you don't have the Solaris 10 x86 nfssrv patch, 138071-01. One telltale, beyond lots of "NFS server not responding" on the client is a high number of "badcalls" visible with nfsstat. The client would have to be using NFSv4 to hit this issue, btw. Although, I've never heard of it being related to keyboard input - that's a strange angle. The fix for this is included in current OpenSolaris build, btw (from snv_50 onward). Anyway, if you don't have 138071-01 (check with "showrev -p | grep 138071"), maybe install that first, reboot, and see how it goes. You might not have to reinstall. That said, I do agree with Michael about the good stuff in OpenSolaris; I use it all day/every day, and wouldn't want give it up. ;) HTH, - Neil > you'll certainly benefit from all the good stuff that's gone into Nevada > (codename for the on-going development), plus tons of fixes, of course. > > good luck! > Michael _______________________________________________ networking-discuss mailing list [email protected]
