Welcome to iraf.net Monday, May 20 2024 @ 12:42 AM GMT
| Anonymous: Guest |
08/10/1994 05:50PM (Read 1020 times)
|
|
|
|
|
We recently noticed the following quirk in IRAF 2.10.2 on HP/UX. If a
user is logged in and has our one tape drive allocated (an Exabyte at
SCSI ID 4, IRAF device mta), other users get the error message "Can't read
kernel memory" when the CL starts and when they try "devstat mta". The
error appears harmless.Stephen Walton, Dept. of Physics & Astronomy, Cal State Northridge
swalton@csun.edu
|
| |
|
|
| Anonymous: Guest |
|
08/10/1994 05:50PM
|
|
|
|
|
Hi Steve,
Weird, I can reproduce it here easily. The message is coming from the
allocation code when it tries to read the process table to see if the user
is logged in. This is done at CL startup when cleaning up lok files,
during a devstat or when actually allocating the drive. It does appear to be
harmless but I'll be sure to track it down for the next upgrade (unless you
need a fix sooner of course).Cheers,
Mike Fitzpatrick
|
| |
|
|
| Anonymous: Guest |
|
08/10/1994 05:50PM
|
|
|
|
|
Hello, Mike:> Weird, I can reproduce it here easily.That's good; at least it isn't just me :-) .> It does appear to be
> harmless but I'll be sure to track it down for the next upgrade (unless you
> need a fix sooner of course).As long as it is truly harmless, I can advise my users to just ignore it.
Thanks.Steve
|
| |
|
|
| |
|
"Can't read kernel memory" on HP/UX
