[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

problems with ypbind



Hi all,

   I'm having problems with ypbind in the latest version of nis
(nis 3.3.1-1).  Specifically, two things:  first, after running for some
time, it suddenly starts to repeatedly give a memory violation:

Oct 25 18:58:24 huckleberry kernel: ypbind: memory violation at pc=00000000 rp=120007fa4 (bad address = 00000000) 
Oct 25 18:58:55 huckleberry last message repeated 116958 times

The second problem is a consequence of the first.  According to the change
log, the package began using the multithreaded version of ypbind
(ypbind-mt).  Therefore, as warned in the changelog, there seems to be
four copies running (which is fine).  Normally, "/etc/init.d/nis stop"
works fine, but after the memory violation above, I have to kill 3
processes (one a zombie) by hand.

Since it is an intermittent problem, I'm not quite sure where to start
attacking it....  Any ideas?  If the original uploader wants to debug
this, I'm more than willing to help.

----

A few months back, I asked where I should report bugs like this, and was
told that I should report the bugs here rather than with the Debian bug
tracking system.  I assume this is because the person who compiled the
package for Debian most likely reads this list, and would be faster at
helping fix the problem than the original maintainer (who most likely is
working on an Intel platform).  First, is this still the best place to
report problems?  (I assume so.)  Second, should it be?  I don't
personally mind, but especially if alpha is going to be a stable release,
should a more formal system be set up?

Kevin

-----
Kevin Squire
k-squire@cs.titech.ac.jp
Research Student
Nakajima Research Laboratory
Tokyo Institute of Technology




Reply to: