Hello true64-unix experts,
thanks for the fast responses to the problem that ipcs does not work
on my server, but I have learned "first reboot, then ask" - (I'm not using
WiN...)
After reboot in the maintenance window the problem has gone - don't
know why ???
the answers until now:
Mohan <mkannapa_at_ford.com>
You have to have the "System V devices" in your
kernel build.
Roberto Romani <roberto.romani_at_digital.com>
ipcs(1) command reads /vmunix for symbol information. To check which
kernel you have booted from enter the following command.
sizer -b (Displays the name of the file from which the running
kernel was booted) this should return vmunix if it is something
else then you need to use the
following option with ipcs(1)
ipcs -a -N /vmunix.whatever <---- output from sizer -b
BTW:
I use different kernels, but after boot the name of the booted kernel
gets a symbolic link to /vmunix, because I think that
"ipcs -a -N /bootfile" only works for root if one uses standard
permissions for "/dev/kmem", may be that this is not the best solution,
but - if someone has an easy solution, please mail me)
Thanks again to this great list,
best regards, Rainer
| R.Schwierz_at_physik.tu-dresden.de |
| Rainer Schwierz, Inst. f. Kern- und Teilchenphysik |
| TU Dresden, D-01062 Dresden |
| Tel. ++49 351 463 2957 FAX ++49 351 463 3114 |
|
http://hep.phy.tu-dresden.de/~schwierz/ |
Received on Wed Feb 24 1999 - 07:10:05 NZDT