MESSAGE
| DATE | 2015-10-26 |
| FROM | Rick Moen
|
| SUBJECT | Re: [Hangout-NYLXS] messed up
|
From hangout-bounces-at-nylxs.com Mon Oct 26 21:19:52 2015
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www.mrbrklyn.com (www.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id BA3DD1624D4;
Mon, 26 Oct 2015 21:19:50 -0400 (EDT)
X-Original-To: hangout-at-nylxs.com
Delivered-To: hangout-at-nylxs.com
Received: from linuxmafia.com (linuxmafia.COM [198.144.195.186])
by mrbrklyn.com (Postfix) with ESMTP id 1BD5F1624CD
for ; Mon, 26 Oct 2015 20:40:44 -0400 (EDT)
Received: from rick by linuxmafia.com with local (Exim 4.72)
(envelope-from ) id 1ZqsJb-0000VO-6g
for hangout-at-nylxs.com; Mon, 26 Oct 2015 17:40:39 -0700
Date: Mon, 26 Oct 2015 17:40:39 -0700
From: Rick Moen
To: hangout-at-nylxs.com
Message-ID: <20151027004039.GF30522-at-linuxmafia.com>
References: <562C5A6E.7040908-at-mrbrklyn.com> <562CA0C2.30301-at-my.liu.edu>
<20151025192757.GO32437-at-linuxmafia.com>
<20151026224650.GB2442-at-panix.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20151026224650.GB2442-at-panix.com>
Organization: If you lived here, you'd be $HOME already.
X-Mas: Bah humbug.
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.5.20 (2009-06-14)
X-SA-Exim-Connect-IP:
X-SA-Exim-Mail-From: rick-at-linuxmafia.com
X-SA-Exim-Scanned: No (on linuxmafia.com); SAEximRunCond expanded to false
Subject: Re: [Hangout-NYLXS] messed up
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: NYLXS Discussions List
List-Id: NYLXS Discussions List
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: hangout-bounces-at-nylxs.com
Sender: "hangout"
Quoting Ruben Safir (mrbrklyn-at-panix.com):
> and yes, i have tried to profile the problem through tailing log files.
Well, that's a start.
> I don't see the hang up other than that qrunner is simply not flipping
> the messages that have been assigned to it.
Offhand, I'm not at all sure why and how that would happen. When
pressed to find out where a Unix process is having problems -- and I'm
not very good at this, so it's a last resort -- I've been known to
strace processes of interest and analyse their output. You can
sometimes find, e.g., what syscall the process is spending the bulk of
its time in and check process state over its life cycle.
_______________________________________________
hangout mailing list
hangout-at-nylxs.com
http://www.nylxs.com/
|
|
