i'm having a little problem here with NFS, and trying to track down a
solution.
situation: Solaris 9 NFS server, Linux clients running autofs to mount
homes via nfs. under linux kernel 2.4.[24,25], things work OK.
after an upgrade to 2.6.[3,4,5] kernels, i start getting timeouts
talking to the nfs server - it reports that lockd could not bind
to reserved port (13?). so the clients just lose track of the
server altogether.
my client machines are running debian unstable, with the most
recent versions of all support packages that i can find in the
archives.
anybody got a clue about what's going on? i'd really, really like to get
this fixed so that my test machines are usable again and so that i can
upgrade the rest of our project machines to newer kernels. :)
thanks very much in advance,
elijah
Indiana University
School of Library and Information Science
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs