others). This can happen when your process blocks on pending file
I/O. The process opens a file descriptor, could even be a socket, and
asterisk does only file I/O and network I/O.
file I/O works fine so it can't be a problem (everything else works on the
same filesystem.
get what it's
1. The process hangs in disk wait (flag D in ps' STAT
column). This often means there's a hardware problem
with your disk or controller (or a driver bug), or a
network problem if you use NFS.
not this for sure. no NFS, no filesystem is blocked.
2. The process was suspended
On Saturday 20 September 2008 08:35:53 Wojciech Puchar wrote:
1. The process hangs in disk wait (flag D in ps' STAT
column). This often means there's a hardware problem
with your disk or controller (or a driver bug), or a
network problem if you use NFS.
not this for sure. no
Which I thought was impossible. Neophyte question, no doubt, but
googling was less than helpful (which probably means I'm fubar, no
doubt). Anyway, I have a certain common X app (xmms) that likes to
hang (since my last buildworld, it seems) when when it's right about
to open a file-choosing
On Fri, Sep 19, 2008 at 11:41 AM, Steve Franks [EMAIL PROTECTED] wrote:
Which I thought was impossible. Neophyte question, no doubt, but
googling was less than helpful (which probably means I'm fubar, no
doubt). Anyway, I have a certain common X app (xmms) that likes to
hang (since my last
On Sep 19, 2008, at 10:41 AM, Steve Franks wrote:
The only way to get rid of it is to
reboot. Now, given the behavior, I'd have to suspect something
underlying as the true source of the problem, but shouldn't kill kill
it anyway - I mean, isn't there some way to kill a process that's
stuck
Steve Franks wrote:
Which I thought was impossible. Neophyte question, no doubt, but
googling was less than helpful (which probably means I'm fubar, no
doubt). Anyway, I have a certain common X app (xmms) that likes to
hang (since my last buildworld, it seems) when when it's right about
If you can't kill a process (even with SIGKILL), it means
that the process currently can't be put on the run queue,
because only processes that are able to run can receive
signals. Given that, such a situation usually has one of
these three reasons:
Clearly and I/O block is my specific
