* jack <[email protected]> [05-30-13 12:14]: > I have mutt (built from the hg tip) on a remote linux box. I ssh into > the remote box and then run mutt from the prompt. This has generally > worked fine. In fact, sometimes I open multiple ssh connections to the > remote box and run an instance of mutt in each one. > > Recently, however, I have been leaving the ssh connection, and the > remote instance of mutt, open for longer than, say, 30 minutes while I > go do other things on my local box. I have noticed that when I do this, > eventually I return to find that my ssh connection is still open and > working fine, but mutt has quit. The prompt says: > > Caught signal 15... Exiting. > > Is this a bug? What does "signal 15" mean? > > One time I had four ssh connections to remotebox open, with an instance > of remote mutt open in each. I left them alone for about an hour, and > when I returned all four of them had quit, showing "signal 15". > > The remote box is not mine. I merely rent some space on it.
Just guessing but I would say you are timing out the ssh connections rather than mutt. I do something similar but to a box I own. I run tmux which is similar to screen and maintain a persistant session in which I also run mutt (or two or three instances of mutt) and unattach and reattach as needed from where-ever. When the ssh connection is interrupted, all that is necessary to to open another and reattach the tmux/screen session and mutt is still there as when you left it. googling for ssh and "signal 15" confirms timing out of the connection. If you have other questions about my setup, I am happy to explain. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net
