home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!edcastle!dcs.ed.ac.uk!gdmr
- From: gdmr@dcs.ed.ac.uk (George Ross)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: problems with amd
- Message-ID: <BxLxvF.534@dcs.ed.ac.uk>
- Date: 12 Nov 92 14:35:39 GMT
- References: <92Nov11.1913.4225@crash.canon.co.uk> <1992Nov11.225817.29248@babbage.ece.uc.edu>
- Sender: cnews@dcs.ed.ac.uk (UseNet News Admin)
- Organization: Department of Computer Science, Edinburgh University
- Lines: 30
-
- In article <1992Nov11.225817.29248@babbage.ece.uc.edu>, montjoy@thor.ece.uc.edu (Robert Montjoy) writes:
- > 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
-
- We've been plagued by this kind of thing on several of our machines too. After
- the not responding/OK messages we then get "server can't decode arguments" two
- or three times then things hang up completely. The plock patch cut down on
- the first of these but didn't do anything to solve the real problem. Neither
- did re-nicing amd. Neither did Sun's jumbo lock patch, nor did all the other
- kernel patches I've tried.
-
- We've also had problems with amq getting "RPC: Remote system error", which we
- fixed in a previous version by upping NEXP_AP from 254 to 1022, but that
- doesn't seem to have fixed it this time.
-
- All contributions gratefully received...
- --
- George D M Ross, Department of Computer Science, University of Edinburgh
- Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ
- Tel: 031-650 5147 Internet: gdmr@dcs.ed.ac.uk JANET: gdmr@uk.ac.ed.dcs
-