From: David Gutierrez (davegu1@hotmail.com)
Date: Wed Feb 02 2005 - 15:39:49 EST
Hello to everyone, We are current working on installing lsof on a 5.1b pk3
system and its complaining of:
# lsof
lsof: no proc table space (150994944 bytes)
#
Has anyone seen this error.
My research finds out that some of the headers are not installed in the
configuration file since the same lsof runs fine in a 4.0 version.
We have already done this steps:
Downloaded lsof.
# ./Configure tru64
# make
./lsof -h
Got the list of UNIX dialect abbreviations with:
#Configure -h
Read the distribution's details in 00DIST, the technical details 00DCACHE
and 00PORTING.
* Used the test suite, described in 00TEST, by:
#cd tests
#make
and
#make opt
And verified the following info on 00FAQ as of:
SECTION 7.7 Why does lsof say it can't read the kernel name list or
proc table on Digital UNIX 4.x or Tru64 UNIX?
By default on Digital UNIX 4 and Tru64 UNIX lsof reads the
addresses for kernel symbols with the knlist(3) function.
That function can fail, for example, when the kloadsrv
daemon isn't running or is malfunctioning. When that
happens, lsof may abort with one of these error messages:
lsof: can't read kernel name list from knlist(3): ...
or
lsof: can't read proc table info
The first message suggests a complete knlist(3) or kloadsrv
failure; the second, a partial one.
If you know the name of the file from which the running
system was booted, e.g., /vmunix, you can use lsof's -k
option to direct it to read kernel symbol addresses from
the name list of that file --
$ lsof -k /vmunix ...
If that works, then knlist(3) is malfunctioning and you
need to fix it.
Comments are welcome.
David
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:14 EDT