Hello,
I have a strange problem that is driving me nuts. Sorry if this is
long.
Background: I am a long time mutt user. I use it at home. I use it at
work. I get a lot of email. I love mutt.
The problem is at work. I routinely interact with several servers
(Linux and *BSD). I keep terminals
=- Hal Burgiss wrote on Tue 20.May'08 at 9:30:27 -0400 -=
The problem is at work. I routinely interact with several servers
(Linux and *BSD). I keep terminals with ssh sessions open to all
these. On one of these, I keep my personal mail spool (mbox). This is
a CentOS Linux server. The mutt
On Tue, May 20, 2008 at 05:45:47PM +0200, Rado S wrote:
a) try 1.5.18
OK, good idea. I am running that now, and should know within an hour
or two.
b) I only know of stale NFS handles freezing mutt beyond recovery.
Try with local filesys folder open in mutt all day. If it doesn't
hang, it's
On Tue, May 20, 2008 at 12:13:34PM -0400, Hal Burgiss wrote:
On Tue, May 20, 2008 at 05:45:47PM +0200, Rado S wrote:
a) try 1.5.18
OK, good idea. I am running that now, and should know within an hour
or two.
No go. Still hanging. :(
--
Hal Burgiss
This Mutt hangs/freezes probably 10-15 times a day. It is completely
unresponsive. If I open a second ssh session, and kill the mutt
process, it generally takes maybe 30 seconds for mutt to let go, and
to get a shell prompt back. If I don't manually kill mutt, and just
So you regain control
On Tue, May 20, 2008 at 12:06:28PM -0500, David Champion wrote:
So you regain control of mutt's session when mutt dies to a kill
signal?
Yes. Sometimes quickly. Sometimes after more than 30 seconds or so.
Can you also suspend mutt (control-Z) from within the same session,
or only from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, May 20 at 09:30 AM, quoth Hal Burgiss:
This Mutt hangs/freezes probably 10-15 times a day. It is completely
unresponsive.
Try running mutt in debug mode; with luck, we can see what mutt's
doing when it dies.
~Kyle
- --
He who dares
On Tue, May 20, 2008 at 12:26:54PM -0500, Kyle Wheeler wrote:
Try running mutt in debug mode; with luck, we can see what mutt's
doing when it dies.
Thanks! I wasn't aware of debug mode, but I'm game. Rebuilt now and
running -d 5 now.
--
Hal Burgiss
DBSInteractive
Technical Services
Try enabling SSH keepalives.
On Tue, May 20, 2008 at 06:01:10PM +, Jussi Peltola wrote:
Try enabling SSH keepalives.
Thanks. I have keepalives enabled on the server end already.
--
Hal Burgiss
DBSInteractive
Technical Services
On Tue, May 20, 2008 at 12:26:54PM -0500, Kyle Wheeler wrote:
Try running mutt in debug mode; with luck, we can see what mutt's
doing when it dies.
All I get is ...
Caught signal 15... Exiting.
That is from killing the mutt process after its hung.
--
Hal Burgiss
DBSInteractive
Technical
On Tue, May 20, 2008 at 12:06:28PM -0500, David Champion wrote:
So you regain control of mutt's session when mutt dies to a kill signal?
Can you also suspend mutt (control-Z) from within the same session, or
only from outside?
I've had two opportunites to try control-z. Both times it worked,
On Tue, May 20, 2008 at 01:46:59PM -0700, Gary Johnson wrote:
The debug output is sent to a file, not to your terminal. The
latest debug file will have the name ~/.muttdebug0.
Ach! Thanks. Wasn't expecting that. Now have 5 different ones, and its
a little hard to see where the problem might
On 2008-05-20, Hal Burgiss [EMAIL PROTECTED] wrote:
On Tue, May 20, 2008 at 01:46:59PM -0700, Gary Johnson wrote:
The debug output is sent to a file, not to your terminal. The
latest debug file will have the name ~/.muttdebug0.
Ach! Thanks. Wasn't expecting that. Now have 5 different
On Tue, May 20, 2008 at 02:05:28PM -0700, Gary Johnson wrote:
I should have mentioned this before, but something you can do to
help associate the contents of the debug file with mutt's actions is
to open another terminal and in it run
tail -f ~/.muttdebug0
Excellent! Its going now.
What should a functional control-z tell me?
If control-Z works, your transport (ssh) and terminal are still
fundamentally intact, and responsive to low-level traffic and
out-of-band signals. (It means that mutt is responsive to signals too,
for that matter -- once it receives them.) Does mutt
On Tue, May 20, 2008 at 05:09:07PM -0500, David Champion wrote:
What should a functional control-z tell me?
If control-Z works, your transport (ssh) and terminal are still
fundamentally intact, and responsive to low-level traffic and
out-of-band signals. (It means that mutt is responsive
17 matches
Mail list logo
