i have a little problem here.  we have a RH4.2 (intel) machine which has
been happily plodding along as a number crunching workstation for quite a
while.  recently, we have not been able to NFS mount any of it's exported
directories.  check this out:

to debug the problem, i run mountd as root on "gumby" by typing:

[root@gumby /root]# rpc.mountd -Fd call

then, on another machine (RH5.0/Alpha, "munch"), i try to mount an
exported directory: 

[root@munch dpm]# mount gumby:/home/dpm gumby
rpc mount: RPC: Unable to receive; errno = Connection reset by peer

this causes my rpc.mountd on "gumby" to segfault, giving the following
message:

mountd[10984] 04/13/98 08:09 mnt [1 118/4/13 07:12:27 munch.dynatec.com
0.0+0,1,2,3,4,6,10]
        /home/dpm
Segmentation fault (core dumped)

"gumby"'s export file has the following entry for the directory in
question:

/home/dpm      *.dynatec.com(ro,insecure)


some observations:

  - this behavior happens when trying to mount exported directories onto
    RH5.0 boxes (both intel and alpha)

  - our DU/Alpha box CAN mount the exported directories without crashing
    mountd. (?!)

  - both of the RH5.0 boxes have been fully updated w/ Red Hat's RPM's.

  - the only really non-standard thing on the the RH5/Alpha box is that
    we are running egcs-1.0.2 and glibc-2.0.7-6.2.  the RH5/Intel box is
    also running egcs, although i'm not sure what glibc it's running (i
    dont have access to it at the moment).

any help figuring this one out would be greatly appreciated.

-matt

-----------------------------------------------------------------------------
Matthew Nelson
Dynamics Technology, Inc. 
21311 Hawthorne Blvd., Suite 300, Torrance, CA 90503-5610
Voice: (310) 543-5433   FAX: (310) 543-2117   Email: [EMAIL PROTECTED]


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to