I'm working on getting 3.2d-1 working well on a couple of testbed systems
before installing on all the other systems. On one of them, the program
/usr/sbin/os_mibs always dumps core after an indeterminate amount of time,
while the other system seems to have no such trouble.
I've been unable to find much documentation on this. By grokking the
executable, I came up with "/usr/sbin/os_mibs -d -warn -error -trace"
as command line arguments. The "-d" option to prevent daemon mode doesn't
work. And it appears that messages go to syslog rather than stdout/stderr.
I haven't caught it yet dumping core, but I have gotten a message at startup:
WARNING system_method.c line 137: system_initialize can't read kinfo, errno = 22
Anyone know what I should look for to try and make this work?
Jim Wright jwright_at_phy.ucsf.edu Keck Center for Integrative Neuroscience
415-502-4874 voice 513 Parnassus Ave, Room HSE-802, Box 0444
415-502-4848 fax UCSF, San Francisco, CA 94143-0444
Received on Wed Mar 27 1996 - 02:51:06 NZST