On 15 Jan 2010, at 01:00, Ben Finney <ben+deb...@benfinney.id.au> wrote:
On 15-Jan-2010, Mark Brown wrote:
On Fri, Jan 15, 2010 at 11:34:34AM +1100, Ben Finney wrote:
I have upgraded to ‘nis’ 3.17-31. I repeated the same steps repo
rted
in the message (Message-ID: <20090814032406.ga3...@benfinney.id.au>)
with the same results.
Can you reproduce this behaviour, though?
This question confused me the first time you asked it, and I'm no
closer to knowing what you mean. How is what I wrote above not an
answer to that question?
As I reported, I can reproduce the behaviour, by following the same
steps as I documented. So I can only conclude that your question must
mean something else, but I don't know what.
I mean "can you make this happen again?" - having reproduced something
isn't the same as being able to so so repeatedly and it hasn't been
clear to me that you were able to see this regularly. Clearly there's
more information than just the steps you gave needed or all users
would be experiencing this.
If you can reproduce the problem then a 'ps amxw' snapshot and a
strace of what ypbind is up to would both be good starts - note that
ypbind is multi-threaded which will probably mean stracing each
individual thread if it's already running.
I don't know what exactly you need from me for the ‘strace’. Can y
ou
tell me what commands to run?
Find all the pids for ypbind and run strace -p on them, or if you can
reproduce from the command line try starting with strace -f (though
this may mask symptoms and will be much more verbose).
The ‘ypbind’ is currently still failing, so attached is the ‘ps
amxw’
snapshot.
Your network configuration and yp.conf
may also be handy if you're able to supply them.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
