home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!malgudi.oar.net!ucbeh.san.uc.edu!ucunix.san.uc.edu!babbage.ece.uc.edu!thor.ece.uc.edu!montjoy
- Newsgroups: comp.sys.sun.admin
- Subject: Re: problems with amd
- Message-ID: <1992Nov11.225817.29248@babbage.ece.uc.edu>
- From: montjoy@thor.ece.uc.edu (Robert Montjoy)
- Date: Wed, 11 Nov 1992 22:58:17 GMT
- Sender: root@babbage.ece.uc.edu (Operator)
- References: <92Nov11.1913.4225@crash.canon.co.uk>
- Organization: Unversity of Cincinnati, ECE Dept
- Nntp-Posting-Host: thor.ece.uc.edu
- Lines: 32
-
-
-
- Hi.
-
- In article <92Nov11.1913.4225@crash.canon.co.uk> tim@crash.canon.co.uk writes:
- >We're running amd5.3beta (alpha #1) to look after the nfs mount
- >requirements on our network of sun4s. However, sometimes we have machines
- >hanging up, seemingly waiting for amd. The syslog message:
- >
- >Oct 22 11:03:13 crash vmunix: NFS server amd:140 not responding still trying
- >Oct 22 11:03:33 crash vmunix: NFS server amd:140 ok
-
- What is happening is amd is getting "swapped" out. You should
- patch amd to lock the text pages of amd into memory. This should eliminate
- most of these messages. You will need to add the plock system call.
- Something like this
-
- plock(PROCLOCK);
-
- needs to be added into the main of amd.
- You will also need to include <sys/lock.h>( #include <sys/lock.h>).
-
- There was a patch avaliable from at the following location.
- csri.toronto.edu:pub/edwin/amd.plock_patch, amd.README
- --
- Rob Montjoy - Rob.Montjoy@UC.Edu
- Computer Engineer - montjoy@ucbeh.BITNET
- University of Cincinnati - montjoy@babbage.ece.uc.edu
- Electrical and Computer Engineering - uunet!uceng!rmontjoy
-
- -- To Save the Earth. The Humans must die.
-
-