I received three Replies to the message I posted
Thanks to :
Richard Bemrose
Lew Randerson
Alan_at_ nabeth
I have tried the ideas they put forward such i.e.
Permissions of /dev/kmem and of the monitor program
and checked the group setup
Alan sent
If the file /dev/kmem really didn't exist you'd get the
message:
monitor: live: Can't open /dev/kmem: No such file or directory.
The "No such device or address" message occurs when Monitor
tries to read from a kernel address that doesn't exist or
is protected. The Freeware CDROM version may include some
disk collection code that doesn't work reliably on all systems
(it worked on all mine...). To verify, use the data collection
option to limit what it tries to collect and see if the problem
only occur when collecting disk data.
If it is the disk collection problem and you can recompile
from sources, remove the -DNEXUS_LIST option from the line
of constant definitions in the Makefile and recompile. If
you can't recompile, there is a newer version on gatekeeper.dec.com
in /pub/DEC/monitor.alpha.tar.Z that does a better job of getting
disk queue statistics on recent versions.
this I have not fully explored yet but if it does help I will post again
Thanks for the help
Regards
Nick L
***********************
Original Post
***********************************
Hi all,
I believe this is in the archives but I cannot find it
I have 4 x4.0d machines on two the Freeware program monitor works fine
on the other two it crashes out with :
monitor: curses: window size is 0x0
monitor: read_kernel: can't read from /dev/kmem: no such device or address
kmem does exist in /dev/ and there seems to be no major difference between
the machines that work and those that do not
The original 4.0d disk was copied twice and it is the copies that fail to work !!
they were copied by dd.
I will Summerise
any ideas ??
Regards
Nick Leonard
Systems Admin
Poole Hospital NHS Trust
Nick Leonard
Systems Administrator
Poole Hospital NHS Trust
Received on Wed Oct 27 1999 - 15:17:10 NZDT